Adaptavist Cloud Apps

Development

Website

Resolving…

Description

Adaptavist builds apps and integrations for Atlassian products (Jira, Confluence, Trello). It provides cloud apps, automation, and development tools for teams using the Atlassian ecosystem.

Status Page

https://status.connect.adaptavist.com

Active Incidents

Last refresh: 2026-10-17 20:12 UTC (1h ago)

Disabled ScriptRunner validators/conditions enforced again

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

Incident

Location: —

Started: 2026-10-09 18:43 UTC (8d ago)

Updated: 2026-10-16 13:38 UTC (1d ago)

Resolved: N/A

2026-10-12 16:08 UTC (5d ago) : Correction: the update posted on 12 October at 15:57 UTC was intended for a different incident and does not apply here. This incident, ScriptRunner validators and conditions that were disabled being enforced again after a workflow is edited and published, remains open. We are still working with Atlassian on a fix and on correcting rules already affected. The workaround above still applies. We a...

2026-10-12 15:57 UTC (5d ago) : 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 entere...

2026-10-09 18:43 UTC (8d ago) : 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 Atla...

Post function Experiencing Delayed Execution

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

Incident

Location: —

Started: 2026-10-08 12:53 UTC (9d ago)

Updated: 2026-10-12 22:10 UTC (4d ago)

Resolved: N/A

2026-10-12 08:20 UTC (5d ago) : 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.

2026-10-08 12:53 UTC (9d ago) : 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.

Jira expression conditions fail with “Action N is invalid” when the transition screen sets a field the condition checks

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 entere...

Incident

Location: —

Started: 2026-10-12 16:09 UTC (5d ago)

Updated: 2026-10-12 16:09 UTC (5d ago)

Resolved: N/A