72 recorded Adaptavist Cloud Apps incidents since June 2025, with official updates, affected components, duration and resolution information.
We have identified that one of the services in the US froze between 19:26 and 19:35 UTC on Oct 17 and between 16:10 and 16:33 UTC on Oct 18, losing a portion of the events affecting a few customers.
We have identified the cause of the issue with Behaviours causing the Behaviours list to not load for a small number of customers. We are currently working on creating a fix for the issue and will post a further update for this issue once a fix has been deployed.
The root cause of this incident has been identified, and a fix soon will be deployed.
We have deployed a fix to resolve the issue and will continue to monitor our services to ensure the incident is fully resolved. We apologise for any inconvenience caused.
Our monitoring has now confirmed that the incident has been resolved and that the behaviours list is loading as normal again. We apologise for any inconvenience caused.
We have identified the root cause of the issue with the Workflow Functions service, causing transitions to fail with "Action N is invalid" when a ScriptRunner "Restrict transition" condition checks a field that the same transition's screen fills in. Atlassian has confirmed this is a defect in Jira Cloud: Forge workflow conditions are re-evaluated at execution time against the values just entered on the transition screen instead of the stored work item. It is tracked by Atlassian as https://jira.atlassian.com/browse/ECO-1851. The fix must come from Atlassian; we recommend watching and voting for that ticket. Only conditions that reference a field on the transition's screen are affected. Validators and post functions are not affected. We'll provide an update when Atlassian ships a fix. We apologise for any inconvenience caused and thank you for your patience.
We continue to discuss potential approaches with Atlassian, who are still investigating and working towards a fix. The issue remains tracked under https://jira.atlassian.com/browse/ECO-1851. We recommend watching and voting for the ticket to help prioritise it. We’ll provide another update when there is further progress or when Atlassian ships a fix. Thank you for your continued patience.
We expect a fix from Atlassian to be released by early next week. We will post another update once we confirm it resolves the issue.
We've identified an issue where admin pages are not loading for a subset of customers, we are investigating a fix for this now Apologies for any inconvenience caused
We have identified the root cause, the issue only affects connect admin pages We have identified the root cause: this issue only affects the Connect admin pages. Workaround: Please use the Forge ScriptRunner admin pages instead. You can access them via the Apps sidebar: 1. In the sidebar, select the top ScriptRunner app. 2. Look for the Forge admin pages, which feature a cog icon to the left of each page name.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified the root cause of an issue with the Workflow Rules service, causing validators and conditions that are disabled in ScriptRunner to be enforced by Jira again after a workflow is edited and published. Workaround: in ScriptRunner → Workflows, Enable and then Disable the affected rule again, or delete it. This does not affect other rules. Our engineering team is working with Atlassian on a fix and preparing a correction for rules already affected. We’ll provide an update shortly. We apologise for any inconvenience caused and thank you for your patience.
Edit: this update was posted incorrectly and has now been removed
Updated: We are actively working with Atlassian on a fix. The workaround below still applies. We apologise for any inconvenience and thank you for your patience.
A fix has been released that prevents this issue from occurring on workflows going forward. Rules that were already affected prior to the fix remain in a broken state, and we're continuing to work with Atlassian to identify the complete list of impacted customers
We are now in the process of contacting affected customers. As a fix for this has been released and tested 1 week ago and the issue should not be occurring anymore, marking this incident as resolved. This incident has been resolved.
We have identified that workflow post functions are executing late because post function invocation events are being delivered late to ScriptRunner by Atlassian's Forge platform. We have raised this with Atlassian and are awaiting their investigation. We’ll provide an update shortly. We apologise for any inconvenience caused and thank you for your patience.
We can confirm that Atlassian have confirmed that the source of the delays is being caused by them sending us the events late. We are awaiting Atlassian to implement a fix for this issue and will provide an update once they have done this.
We have identified the root cause of the delayed execution of script listeners and workflow post functions. Forge product events and post function invocations are intermittently delivered late to ScriptRunner by Atlassian’s Forge platform, typically during peak periods. Atlassian is tracking this as a Forge platform defect under https://jira.atlassian.com/browse/ECO-1848. The fix must come from Atlassian; we recommend watching and voting for that ticket. We’ll provide an update when Atlassian ships a fix. We apologise for any inconvenience caused and thank you for your patience.
We are still waiting for a fix from Atlassian. This continues to be tracked as a Forge platform defect under ticket https://jira.atlassian.com/browse/ECO-1848. We encourage you to watch and vote for that ticket to help prioritize it. We'll post again as soon as there's movement from Atlassian or any change on our end. Thank you for your continued patience.
Our monitoring has detected delays in event delivery again. We continue to monitor event delivery delays
We have identified that script listeners timed out approximately between 7 pm UTC on Oct 2 and 1 am UTC on Oct 3 due to the events spike from 1 customer, affecting other customers
We have identified that event processor EU froze in the morning of 2nd October, losing events affecting multiple customers
We have identified an issue that is causing Enhanced Search filters that contain Enhanced Search JQL Keywords and functions to be overwritten with the translated JQL query. We are working to restore the affected filters to the original query. Please avoid making an update to your filter if you can see the Enhanced Search function has been overwritten, and we will restore it for you as soon as possible.
Data recovery is underway and expected to complete in a few days. Thank you for your patience. If you need immediate assistance, please submit a support ticket.
Recovery operations are now complete. We have restored all retrievable Enhanced Search original filter queries. Please note that a small number of filters could not be recovered. If your Enhanced Search filter is no longer visible in the Enhanced Search application, please contact our support team for immediate assistance and manual restoration. We will be reaching out to affected customers where further details are needed.
On 01st Oct 2026, between 01:00 UTC and 07:25 UTC Atlassian experienced this incident https://developer.status.atlassian.com/incidents/2ypy8lwt1prw The consequence of that problem meant that ScriptRunner for Jira Cloud, ScriptRunner for Confluence Cloud and Enhanced Search stopped receiving critical authentication information that is required for the apps to be able to make requests to Atlassian's REST APIs.
We are investigating issues with the workflow edit page not loading.
We have identified the issue and have reported it to Atlassian to resolve it. We will update this page when there is a change.
We have identified the issue and isolated it to the post functions with very large scripts. Affected users can continue to edit scripts using the Script Runner Workflows page. Our team is actively working on a solution. We apologise for the inconvenience and appreciate your patience.
We are continuing to work on a fix for this issue that prevents workflows with large scripts from loading. We advise all customers experiencing this issue to edit the affected post function using the Workflows Admin page. Once on this page, we advise you to copy the script and add it to Script Manager as a script file. After doing this, you can then replace the inline script with the script file, which will reduce the post function size and allow it to start loading correctly again in the Jira Workflow.
We are still continuing to work on a fix for this issue and advise any customers affected by this issue to use the workaround provided in our previous update. We apologise for any inconvenience caused by this issue.
We are now working with Atlassian on a fix. We’ll provide an update shortly. Thank you for your patience.
A fix has been implemented and the service is now being closely monitored to ensure the issue remains resolved. We will provide another update once monitoring is complete or if there are any further changes. Thank you for your patience.
This issue has been resolved. Please let us know if you experience any further problems, and thank you for your patience.
We have confirmed an issue with when trying to resolve the `issue` variable in postfunction executions. We are looking to resolve this issue.
We have enabled a fix for the `issue` variable, and will continue to monitor post function executions
We have confirmed that the issue has resolved. Apologies for the inconvenience caused.
Some executions may have failed to complete on Sep 11 2026, between 16:00 UTC and 18:00 UTC due to an infrastructural bottleneck that has since been identified and sorted out.
Some unexpected errors may have affected the execution of some script listeners in the past 48 hours. We have rolled back a change that is likely to have caused this issue and are monitoring the performance of the application.
Only a handful of customers were impacted, and the incident was mitigated by rolling back the deployed changes.
A small number of scripts failed to run between 9:01am UTC and 9:59am UTC on the 27th Aug 2026. The issue is now resolved and scripts should be running normally. This affected ScriptRunner for Jira and Confluence Cloud. Apologies for any inconvenience caused.
We have identified script execution delays for Listeners and Workflows. The solution has been implemented and we are slowly processing the events and therefore executing the delayed scripts. This affects ScriptRunner for Jira Cloud and Confluence Cloud
We have patched the environment to start processing script execution requests again. Script executions are back to normal.
We’re confident the ScriptRunner Cloud issues are now resolved, so we’re closing this incident. If you experience any further issues, please contact our team.
Between 10:15 and 10:30 UTC, customers using ScriptRunner for Jira Cloud or Enhanced Search apps may have experienced increased rate limiting when accessing Jira REST APIs from their scripts, other automations or JQL searches. This was caused by a gradual release of Atlassian's new authentication mechanism for requests made as individual users. We rolled back the changes and apologise for any disruption.
We have identified an issue where ScriptRunner conditions and validators are failing to load on the Jira Workflows screen when the Workflow is in draft mode As a workaround users can edit their conditions and validators via the ScriptRunner workflows admin page Apologies for any inconvenience caused
The issue is caused by the deprecation of the legacy workflows page https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Final-notice-old-workflow-editor-deprecation-in-July-2026/ba-p/3247499 For users to edit their conditions and validators they will need to follow the instructions above to use the new workflow editor experience or edit their conditions and validators via the ScriptRunner Workflows Admin Page Thanks!
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We have identified an issue that is causing ScriptRunner migrations from DC to Cloud to fail. We are currently working on releasing a fix and will provide another update once the issue is resolved. We advise that migrations are not initiated until we have confirmed the fix is released, as any migrations to Cloud will currently fail.
A fix has been implemented to resolve the failing ScriptRunner migrations, and we are currently monitoring the system to ensure stability. Cloud migrations can now be initiated. If you encounter any further issues with your ScriptRunner Cloud migration, please raise a support ticket with our team.
ScriptRunner Cloud migrations are operating normally. The underlying issue has been addressed, and we are monitoring the system to ensure continued stability. Thank you for your patience.
