/
Time to SLA – JQL Failure: Search limit exceeded with OpenSearch enabled

Time to SLA – JQL Failure: Search limit exceeded with OpenSearch enabled

Summary

Users may encounter a JQL Failure detected error and see panels (for example, Tempo panel or Time to SLA reports) stuck loading/spinning when OpenSearch is enabled and the search results or index fields exceed platform limits.

Environment

  • Product: Time to SLA

  • Platform: Jira Data Center

  • Host Product Version: 11.3.1

  • App Version: 11.6.0-jira-11

  • Search Engine: OpenSearch

Problem

When OpenSearch is enabled for a Jira instance, SLA reports or panels (such as the Tempo panel or SLA reporting dashboards) may fail to load. Users see a continuous spinning icon followed by an error message:

JQL Failure detected
Search limit exceeded. We couldn't complete your search because it requests [X] results which exceeded the search platform limit of 10,000. Try refining your query or contact your Jira administrator. Repeating the same search may not work.

Symptoms

  • SLA panels keep spinning and do not display data.

  • The issue typically triggers once the work item count or field count approaches or exceeds 10,000.

  • The error specifically references a “search platform limit”.

Cause

OpenSearch (and Jira’s OpenSearch integration) has protective limits to maintain cluster performance and prevent memory exhaustion. Two common limits can trigger this behavior:

A) Result window limit (index.max_result_window / Jira jira.search.platform.max.result.window)

  • What it is: A limit on how many results a single search can retrieve/paginate through.

  • Typical default: 10,000

  • Strong indicator: The error message contains wording like:
    “it requests [X] results which exceeded the search platform limit of 10,000”
    This usually points to the result window limit.

  • Jira note: Jira Data Center also enforces this via the property jira.search.platform.max.result.window (default commonly 10,000).

  • See Atlassian guidance:
    https://support.atlassian.com/jira/kb/handling-jql-rest-api-searching-exceeding-max_result_window-in-jira/

B) Field mapping limit (index.mapping.total_fields.limit)

  • What it is: A limit on the number of mapped/indexed fields in the OpenSearch index. Large numbers of custom fields (and complex indexing patterns) can push the mapping count high.

  • Typical default: Varies by deployment/version; in some environments it may be 10,000.

  • Strong indicator: OpenSearch/Jira logs may contain an error like:
    “Limit of total fields [10000] has been exceeded”

  • Atlassian also provides a dedicated health check article for this:
    https://support.atlassian.com/jira/kb/health-check-opensearch-mappings-limit-in-jira-data-center/

Solution / Workaround

Use the option that matches your symptoms and what you see in logs. Option 1 is the recommended first step.

Option 1 (Recommended first): Refine the JQL / reduce the result set

If a query (or an app panel behind the scenes) matches more than 10,000 issues, the request may fail on OpenSearch.

Try narrowing the query so it returns fewer issues. Examples:

  • project = ABC AND updated >= -30d

  • project = ABC AND statusCategory != Done

  • project = ABC AND created >= startOfYear()

Note: Even if the user’s visible JQL is “simple”, dashboards/panels/gadgets may internally run broader searches (for example, fetching large sets for calculations), which can still hit OpenSearch limits.

Option 2: Increase the result window (index.max_result_window) (only if absolutely necessary)

If you confirm the issue is due to the result window (the message says it “requests [X] results”), you may choose to increase the limit.

OpenSearch API example:

PUT /_settings { "index": { "max_result_window": "50000" } }

Important caution: Increasing the result window can significantly increase memory usage and degrade OpenSearch performance. Only raise it if you understand the impact and can monitor cluster health.

Atlassian guidance: https://support.atlassian.com/jira/kb/handling-jql-rest-api-searching-exceeding-max_result_window-in-jira/

Option 3: Increase the mapping limit (index.mapping.total_fields.limit)

If logs indicate you’re hitting the field mapping limit, increase index.mapping.total_fields.limit.

OpenSearch API example:

PUT /_settings { "index" : { "mapping" : { "total_fields" : { "limit" : "40000" } } } }


Managed services / Atlassian-managed:
If using a managed service like Amazon OpenSearch, you may need to adjust these settings via the service console, or contact Atlassian Support (if they manage the cluster for your Data Center environment): https://support.atlassian.com/

Validation & troubleshooting

After applying a workaround:

  • Refresh the affected Jira issue view/dashboard/report and confirm the panel loads.

  • Check Jira logs and OpenSearch logs for limit-related errors.

  • If mappings were previously blocked due to the field limit, a Jira re-index may be required after raising the limit (to ensure missing mappings/data are rebuilt).

FAQ

Q1: We use Amazon OpenSearch (managed). Can we still change these values?

Usually yes, but it depends on your deployment and permissions. You may need to apply settings through your managed service tooling or contact the team managing OpenSearch.

Q2: What if we cannot change OpenSearch/Jira settings?

Refine the JQL (Option 1), reduce the result set via retention/archiving, or contact Atlassian Support for guidance: https://support.atlassian.com/

Additional resources