Is Adaptavist Cloud Apps down?

Some ScriptRunner for Confluence clients are seeing errors when trying to use the application. This is due to authentication errors with Atlassian Cloud APIs. We are working with Atlassian to understand the underlying cause of the issue, and will provide an update when we know more.

We are still working with Atlassian to investigate the problems with ScriptRunner for Confluence. We will provide more information here when it is available.

We have made some progress in identifying the underlying issue causing problematic application behaviour for ScriptRunner for Confluence Cloud. We are working on some potential fixes in collaboration with Atlassian, and will update here when we have more information.

We have rolled out a potential fix for alleviating the errors experienced in ScriptRunner for Confluence Cloud. We will provide more information here when we are confident that the problem is resolved.

We are confident that the fix deployed at about 13:19 UTC is mitigating the issue. It will take up to an hour after the deployment for all affected installations of ScriptRunner for Confluence to start working again. We will provide more information at that time and confirm that the incident is resolved.

We are confident that the issues experienced by Confluence Cloud tenants today and yesterday are now resolved. We are continuing to work with Atlassian to understand the root causes of this issue so that we can better avoid it in the future.

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.

Atlassian has shipped a fix, which we have now applied, and this issue is resolved. Please let us know if you experience any further problems. Thank you for your patience

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.