Intermittent Content Search Failures (Jan 2026)
Severity | P1 |
|---|---|
Status | RESOLVED |
Start Date |
|
End Date |
|
Duration | 4d |
Tickets | ECOHELP-107908 |
Overview
Capable apps (Diagrams, Approval, Calendars, Markdown) are impacted by intermittent Confluence Search API failures, causing unreliable content/user searches and Hystrix/500 errors. Atlassian acknowledges this as P1 but has not posted publicly or provided a timeline for resolution.
Incident Description
The /wiki/rest/api/search endpoints fail sporadically with 400 BadRequestException: "CQL parsed but search manager unable to execute... Hystrix circuit short-circuited and is OPEN"
Spikes occur ~every 6 hours (45-60 min duration, e.g., 12-13 UTC), affecting all sites. Direct API calls succeed, but calls from Marketplace apps fail, rendering features unusable (e.g., user selection in Approval, search results for diagrams or pages etc.).
How do I know if I’m affected?
Any features that depend on using the Confluence Content Search API failed sporadically:
Browsing diagrams from pages
Viewing templates
Searching for content using the search feature
etc.
Workaround
We've thoroughly investigated alternative APIs to bypass the failing CQL search, but none fully replicate dynamic content/user querying in Forge apps.
The only workaround for this Confluence Search API issue is retrying the operation after a 5-10 minute delay, aligning with observed 45-60 minute spike cycles.
Incident Timeline
Date | Time | Event | Party |
|---|---|---|---|
| 12:34 | Initial report of P1 incident | CAPABLE |
13:19 | P1 Confirmed by Atlassian | ATLASSIAN | |
| 01:23 | We confirmed it affects other Marketplace apps | CAPABLE |
01:29 | Atlassian confirm spikes every 6h (12pm, 6pm, 12am UTC); Engineering teams are investigating | ATLASSIAN | |
10.50 | Requested progress report, ETA and public acknowledgement on status.atlassian.com | CAPABLE | |
12.48 | Notified Senior Atlassian engineering staff | CAPABLE | |
13.56 | Dev team continuing to work on issue | ATLASSIAN | |
18.48 | Still occurring, requested public notice | CAPABLE | |
| 20.15 | Escalated further via high priority customers | CAPABLE |
| 10.00 | Incident still ongoing. No communication or updates regarding the issue. | CAPABLE |
| 07.49 | Engineering team has deployed changes. We believe the | ATLASSIAN |