Adaptavist Cloud Apps Status

Identified: The service remains stable. We’re continuing to monitor performance and will share another update if needed.

Identified: Delivery times have improved and the service is more stable today. We’ll continue to monitor and will update you if anything changes.

Identified: Our monitoring has detected delays in event delivery again. We continue to monitor event delivery delays

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

Resolved: 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.

Identified: 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

Identified: 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.

Identified: Edit: this update was posted incorrectly and has now been removed

Identified: 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.

Resolved: 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

Identified: 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.

Identified: 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.

Identified: 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.

Identified: The service remains stable. We’re continuing to monitor performance and will share another update if needed.

Identified: Delivery times have improved and the service is more stable today. We’ll continue to monitor and will update you if anything changes.

Identified: Our monitoring has detected delays in event delivery again. We continue to monitor event delivery delays

Identified: 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.

Identified: 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.

Identified: 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.

Identified: 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.

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.

Monitoring: 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.

Identified: 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.

Investigating: 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.

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

Investigating: 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.