Listeners and Post Functions Experiencing Delayed Execution
Update - The service remains stable. We’re continuing to monitor performance and will share another update if needed.
Oct 27, 2026 - 13:41 UTC
Update - Delivery times have improved and the service is more stable today. We’ll continue to monitor and will update you if anything changes.
Oct 27, 2026 - 11:40 UTC
Update - Our monitoring has detected delays in event delivery again. We continue to monitor event delivery delays
Oct 26, 2026 - 18:09 UTC
Update - 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.
Oct 20, 2026 - 10:30 UTC
Update - 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.
Oct 12, 2026 - 22:10 UTC
Update - 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.
Oct 12, 2026 - 08:20 UTC
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.
Oct 08, 2026 - 12:53 UTC
Uptime over the past 90 days. View historical uptime.
ScriptRunner Degraded Performance
ScriptRunner for Jira Cloud Degraded Performance
Enhanced Search for Jira Cloud Operational
ScriptRunner for Confluence Cloud Operational
ScriptRunner Connect Operational
ScriptRunner for Jira Isolated Cloud Operational
ScriptRunner Migration Suite Operational
Kolekti Operational
Mosaic: Content Formatting Macros, Tabs LaTeX HTML Templates Operational
Forms for Confluence (Surveys, Quizzes, Polls & Votes) Operational
Community Forums for Confluence Operational
Upscale Operational
Hierarchy for Jira Operational
Workflow Steps for Jira Operational
Slack IntegratePlus for monday.com Operational
Recurring Tasks for monday.com Operational
Unlimited Subitems for monday.com Operational
Third-Party Services Operational
Atlassian Jira Cloud Operational
Elastic Cloud (Elasticsearch) Operational
AWS ec2-us-west-2 Operational
AWS lambda-us-west-2 Operational
AWS route53 Operational
AWS cloudfront Operational
AWS lambda-us-west-2 Operational
AWS s3-us-west-2 Operational
AWS sns-us-west-2 Operational
AWS sqs-us-west-2 Operational
AWS elasticache-us-west-2 Operational
AWS rds-us-west-2 Operational
AWS elb-us-west-2 Operational
Atlassian Developer Jira Cloud APIs Operational
Atlassian Developer App listings Operational
Atlassian Developer Evaluations and purchases Operational
Atlassian Developer Search Operational
Atlassian Developer User APIs Operational
Atlassian Confluence Cloud Operational
Jira Core Search Operational
Jira Core Notifications Operational
Jira Core Viewing content Operational
Jira Core Marketplace Operational
Jira Core Authentication and User Management Operational
Jira Core Create and edit Operational
Jira Core Administration Operational
Jira Service Desk Authentication and User Management Operational
Jira Service Desk Service Desk Web Operational
Jira Service Desk Service Desk Portal Operational
Jira Software Administration Operational
Jira Software Authentication and User Management Operational
Jira Software Marketplace Operational
Jira Software Notifications Operational
Jira Software Viewing content Operational
Jira Software Search Operational
Jira Software Create and edit Operational
Confluence Administration Operational
Confluence Comments Operational
Confluence Marketplace Apps Operational
Confluence Search Operational
Confluence View Content Operational
Confluence Notifications Operational
Confluence Authentication and User Management Operational
Confluence Create and Edit Operational
LaunchDarkly Streaming API Operational
LaunchDarkly API Operational
LaunchDarkly Feature flag CDN Operational
AWS lambda-eu-west-1 Operational
AWS s3-eu-west-1 Operational
AWS dynamodb-eu-west-1 Operational
AWS cloudwatch-eu-west-1 Operational
AWS sns-eu-west-1 Operational
AWS sqs-eu-west-1 Operational
AWS apigateway-eu-west-1 Operational
AWS kms-eu-west-1 Operational
Auth0 User Authentication Operational
Auth0 Machine to Machine Authentication Operational
Auth0 Multi-factor Authentication Operational
Auth0 Management API Operational
AWS sns-us-east-1 Operational
AWS lambda-us-east-1 Operational
Slack Apps/Integrations/APIs Operational
Intercom Intercom APIs Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Oct 28, 2026

No incidents reported today.

Oct 27, 2026

Jira expression conditions fail with “Action N is invalid” when the transition screen sets a field the condition checks
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
Oct 27, 20:23 UTC
Update - 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.
Oct 21, 09:36 UTC
Update - 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.
Oct 20, 10:41 UTC
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.
Oct 12, 16:09 UTC
ScriptRunner for Confluence installations unable to authenticate with Confluence Cloud APIs
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.
Oct 27, 14:29 UTC
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.
Oct 27, 13:55 UTC
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.
Oct 27, 13:27 UTC
Update - 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.
Oct 27, 12:10 UTC
Update - We are still working with Atlassian to investigate the problems with ScriptRunner for Confluence. We will provide more information here when it is available.
Oct 27, 10:39 UTC
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.
Oct 27, 09:31 UTC

Oct 26, 2026

Disabled ScriptRunner validators/conditions enforced again
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.
Oct 26, 16:15 UTC
Update - 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
Oct 16, 13:38 UTC
Update - 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.
Oct 12, 16:08 UTC
Update - Edit: this update was posted incorrectly and has now been removed
Oct 12, 15:57 UTC
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.
Oct 9, 18:43 UTC

Oct 25, 2026

No incidents reported.

Oct 24, 2026

No incidents reported.

Oct 23, 2026

No incidents reported.

Oct 22, 2026

No incidents reported.

Oct 21, 2026

Oct 20, 2026

Loss of events for multiple customers in US on 17th and 18th October
Resolved - 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.
Oct 20, 01:27 UTC

Oct 19, 2026

No incidents reported.

Oct 18, 2026

No incidents reported.

Oct 17, 2026

No incidents reported.

Oct 16, 2026

Oct 15, 2026

Workflow edit page falling to load
Resolved - This issue has been resolved. Please let us know if you experience any further problems, and thank you for your patience.
Oct 15, 12:59 UTC
Monitoring - 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.
Oct 13, 10:17 UTC
Update - We are now working with Atlassian on a fix. We’ll provide an update shortly.
Thank you for your patience.
Oct 10, 01:26 UTC
Update - 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.
Oct 2, 09:42 UTC
Update - 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.
Oct 1, 15:55 UTC
Update - 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.
Oct 1, 13:49 UTC
Identified - We have identified the issue and have reported it to Atlassian to resolve it. We will update this page when there is a change.
Sep 30, 10:19 UTC
Investigating - We are investigating issues with the workflow edit page not loading.
Sep 30, 09:26 UTC
Behaviours fail to load due to payload size exceeding Forge 5MB response limit
Resolved - 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.
Oct 15, 07:30 UTC
Monitoring - 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.
Oct 14, 10:05 UTC
Update - The root cause of this incident has been identified, and a fix soon will be deployed.
Oct 14, 09:17 UTC
Identified - 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.
Oct 13, 10:26 UTC

Oct 14, 2026

Incident History Powered by Atlassian Statuspage