- Detected by Pingoru
- Jun 16, 2026, 12:31 PM UTC
- Resolved
- Jun 16, 2026, 02:55 PM UTC
- Duration
- 2h 24m
Affected: ScriptRunner for Jira CloudScriptRunner for Confluence Cloud
Timeline · 3 updates
-
identified Jun 16, 2026, 12:31 PM UTC
Between 09:45 on 15/06/2026 and 09:14 on 16/06/2026 (UTC), intermittent caching errors caused ScriptRunner to temporarily fall back to default app settings for some customers. This may have affected scheduled job timing (defaulting to UTC), script timezones, and admin notification behaviour. We have identified the cause and are deploying a fix.
-
monitoring Jun 16, 2026, 12:31 PM UTC
A fix has been deployed and affected settings have returned to normal. We will continue to monitor to confirm full resolution.
-
resolved Jun 16, 2026, 02:55 PM UTC
Our monitoring has confirmed the fix has worked. We’ll continue reviewing the incident to help prevent recurrence. Once more, we apologise for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 15, 2026, 02:55 PM UTC
- Resolved
- Jun 16, 2026, 07:38 AM UTC
- Duration
- 16h 42m
Affected: Forms for Confluence (Surveys, Quizzes, Polls & Votes)
Timeline · 3 updates
-
identified Jun 15, 2026, 02:55 PM UTC
We have identified the root cause of the issue with Forms for Confluence, causing error to some forms and are implementing a mitigation. Our engineering team is actively working to restore service by fixing the issue We’ll provide an update shortly. We apologise for any inconvenience caused and thank you for your patience.
-
investigating Jun 15, 2026, 02:58 PM UTC
We have identified and are investigating an issue with the Forms for Confluence service, which is causing error in some forms. Our engineering team is actively working to determine the cause and impact. We’ll provide an update shortly. We apologise for any inconvenience caused.
-
resolved Jun 16, 2026, 07:38 AM UTC
Our monitoring has now confirmed that the issue with the Forms for Confluence service, causing errors in some forms has been resolved and that all systems and services are operating normally. We’ll continue reviewing the incident to help prevent recurrence. Once more, we apologise for any inconvenience caused and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jun 04, 2026, 06:52 PM UTC
- Resolved
- Jun 04, 2026, 07:27 PM UTC
- Duration
- 34m
Affected: ScriptRunner for Confluence Cloud
Timeline · 3 updates
-
investigating Jun 04, 2026, 06:52 PM UTC
Custom macro editing and deletion are failing in ScriptRunner for Confluence Cloud. We are currently investigating the issue. Custom macro creation is working as expected; the problem only affects editing and deleting existing custom macros.
-
investigating Jun 04, 2026, 07:21 PM UTC
We have identified the root cause of the issue and are currently working on a fix. We'll provide another update as soon as we have more information.
-
resolved Jun 04, 2026, 07:27 PM UTC
The issue has been fixed and the fix has been deployed. We are now monitoring the situation.
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 10:01 AM UTC
- Resolved
- Jun 01, 2026, 01:43 PM UTC
- Duration
- 3h 41m
Affected: ScriptRunner for Jira Cloud
Timeline · 4 updates
-
investigating Jun 01, 2026, 10:01 AM UTC
We have identified an issue with the script executions on May 28th 2026 that might be affecting some customers. Our team is actively investigating the cause and working to determine the appropriate resolution.
-
identified Jun 01, 2026, 10:05 AM UTC
We have identified the cause of the issue. Our team is currently implementing and validating a fix. We will provide further updates as we make progress
-
monitoring Jun 01, 2026, 11:28 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jun 01, 2026, 01:43 PM UTC
At 13:21 28th May 2026 to 07:34 29th May 2026 UTC, there was an issue affecting script executions.
Read the full incident report →
- Detected by Pingoru
- May 06, 2026, 07:46 AM UTC
- Resolved
- May 06, 2026, 07:46 AM UTC
- Duration
- —
Affected: ScriptRunner for Jira CloudScriptRunner for Confluence Cloud
Timeline · 1 update
-
resolved May 06, 2026, 07:46 AM UTC
Script Manager was unaccessible for a few hours between approximately 13:00 UTC and 22:00 UTC on 2026-05-05. Its visibility and accessibility have been restored. Script executions were unaffected.
Read the full incident report →
- Detected by Pingoru
- Apr 30, 2026, 09:42 AM UTC
- Resolved
- Apr 30, 2026, 03:00 PM UTC
- Duration
- 5h 18m
Affected: ScriptRunner for Jira CloudScriptRunner for Confluence Cloud
Timeline · 3 updates
-
monitoring Apr 30, 2026, 09:42 AM UTC
Atlassian is experiencing intermittent delays in wehbook delivery (as per Atlassian's status page). ScriptRunner users who rely on Atlassian events for the triggering of their scripts may subsequently be affected by such delays. We're monitoring the situation and will provide updates when available.
-
monitoring Apr 30, 2026, 02:30 PM UTC
Atlassian has announced that the rollout of the fix for delays in delivering events has completed. They're currently monitoring the situation and will give updates once they can confirm the effectiveness of the fix.
-
resolved Apr 30, 2026, 03:00 PM UTC
Atlassian published an update to their status page that their monitoring confirmed the issue with delays in delivering events is now resolved
Read the full incident report →
- Detected by Pingoru
- Apr 20, 2026, 09:51 AM UTC
- Resolved
- Apr 21, 2026, 11:35 AM UTC
- Duration
- 1d 1h
Affected: Behaviours - ScriptRunner for Jira Cloud
Timeline · 4 updates
-
investigating Apr 20, 2026, 09:51 AM UTC
We have identified an issue with the Behaviours App which is causing it to fail when trying to install the app from the Atlassian Marketplace. We are currently investigating what is causing this issue and will post a further update here once we have identified what is causing the issue. We apologise for any inconvenience caused.
-
identified Apr 21, 2026, 07:45 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 21, 2026, 08:14 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 21, 2026, 11:35 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 17, 2026, 07:27 AM UTC
- Resolved
- Apr 20, 2026, 11:32 AM UTC
- Duration
- 3d 4h
Affected: Behaviours - ScriptRunner for Jira Cloud
Timeline · 4 updates
-
investigating Apr 17, 2026, 07:27 AM UTC
We have an identified an issue with the Behaviours App in the Atlassian Marketplace which is causing it to be hidden and unable to be installed. We are currently investigating what is causing this issue and will post a further update here once we have identified what is causing the issue. We apologise for any inconvenience caused.
-
identified Apr 20, 2026, 06:26 AM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Apr 20, 2026, 08:16 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Apr 20, 2026, 11:32 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 16, 2026, 08:17 AM UTC
- Resolved
- Apr 16, 2026, 08:56 AM UTC
- Duration
- 38m
Affected: ScriptRunner for Jira CloudEnhanced Search for Jira CloudScriptRunner for Confluence Cloud
Timeline · 4 updates
-
investigating Apr 16, 2026, 08:17 AM UTC
We are seeing webhook processing for certain types of events fail with authentication errors. We are looking into the problem and will update here more when we have more information.
-
identified Apr 16, 2026, 08:31 AM UTC
We believe we have identified a resolution to the webhook processing issues we have been experiencing this morning. We are currently validating that this solution has mitigated the errors.
-
monitoring Apr 16, 2026, 08:46 AM UTC
The solution seems to have mitigated the issues we were seeing this morning. We are continue to monitor the situation closely.
-
resolved Apr 16, 2026, 08:56 AM UTC
We are confident that the issues we were seeing with processing event webhooks are resolved now. Please get in touch with our team if you experience any more issues.
Read the full incident report →
- Detected by Pingoru
- Apr 13, 2026, 10:31 AM UTC
- Resolved
- Apr 13, 2026, 10:31 AM UTC
- Duration
- —
Affected: ScriptRunner for Jira CloudBehaviours - ScriptRunner for Jira CloudEnhanced Search for Jira CloudScriptRunner for Confluence Cloud
Timeline · 1 update
-
resolved Apr 13, 2026, 10:31 AM UTC
At 9:59 to 10:02 UTC (10:59 to 11:02 BST), there was an outage for ScriptRunner and EnhancedSearch apps in the US region only.
Read the full incident report →
- Detected by Pingoru
- Mar 25, 2026, 11:40 AM UTC
- Resolved
- Mar 25, 2026, 11:45 AM UTC
- Duration
- 4m
Affected: ScriptRunner for Jira Cloud
Timeline · 2 updates
-
identified Mar 25, 2026, 11:40 AM UTC
We have identified that some requests within customer scripts failed on 24/03/2026 between 16:27 -> 19:52 UTC
-
resolved Mar 25, 2026, 11:45 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 03:06 PM UTC
- Resolved
- Mar 13, 2026, 12:47 AM UTC
- Duration
- 9h 41m
Affected: ScriptRunner for Confluence Cloud
Timeline · 5 updates
-
identified Mar 12, 2026, 03:06 PM UTC
Macros are currently impacted due to an Atlassian platform incident.
-
identified Mar 12, 2026, 03:23 PM UTC
We continue to monitor the Atlassian incident affecting Scriptrunner macros. We will provide updates as more information becomes available.
-
identified Mar 12, 2026, 06:42 PM UTC
We are still monitoring the Atlassian incident for Macros outage, that is impacting the scriptrunner macros. We will update once we see the change in status on Atlassian status page
-
monitoring Mar 13, 2026, 12:36 AM UTC
Atlassian has resolved the incident affecting macro functionality. We are monitoring to ensure services is stable.
-
resolved Mar 13, 2026, 12:47 AM UTC
Our monitoring has now confirmed that the issue affecting macro functionality has been resolved and that services are running normally again. We apologise for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 10:30 AM UTC
- Resolved
- Mar 12, 2026, 10:31 AM UTC
- Duration
- 28s
Affected: ScriptRunner for Jira Cloud
Timeline · 2 updates
-
identified Mar 12, 2026, 10:30 AM UTC
A small minority of scripts failed to run between 11th March 03:24 UTC and 12th March 08:25 UTC due to excessive load on the ScriptRunner execution environment and hitting rate limits with our hosting provider. This was due to an unexpected and significant spike in script execution demand.
-
resolved Mar 12, 2026, 10:31 AM UTC
At 08:25 UTC the execution demand dropped to normal levels and the system resumed normal operation.
Read the full incident report →
- Detected by Pingoru
- Feb 25, 2026, 05:33 PM UTC
- Resolved
- Feb 25, 2026, 05:35 PM UTC
- Duration
- 2m
Affected: ScriptRunner for Jira CloudScriptRunner for Confluence Cloud
Timeline · 2 updates
-
identified Feb 27, 2026, 02:20 PM UTC
Some scripts failed to run between 17:33 UTC and 17:35 UTC due to excessive load on the ScriptRunner execution environment and hitting rate limits with our hosting provider. This was due to an unexpected and significant spike in script execution demand.
-
resolved Feb 27, 2026, 02:23 PM UTC
At 17:35 the execution demand dropped to normal levels and the system resumed normal operation.
Read the full incident report →
- Detected by Pingoru
- Feb 20, 2026, 02:16 PM UTC
- Resolved
- Feb 20, 2026, 06:42 PM UTC
- Duration
- 4h 25m
Affected: ScriptRunner for Jira Cloud
Timeline · 8 updates
-
identified Feb 20, 2026, 02:16 PM UTC
We are currently experiencing delays in filter syncing in SR Enhanced Search US. Filter results may be out of date temporarily until the issue is resolved. We have identified the root cause and working on a potential fix.
-
monitoring Feb 20, 2026, 02:41 PM UTC
A potential fix is being deployed and will be monitored on production shortly.
-
monitoring Feb 20, 2026, 03:24 PM UTC
While we continue to monitor the situation, the ES filters can be manually synced as a workaround in the meantime.
-
monitoring Feb 20, 2026, 03:30 PM UTC
ES filters are starting to be automatically synced again; we'll continue to monitor the situation until we can confirm the issue is fully resolved. In the meantime, manual filter syncing is also possible as a temporary workaround.
-
monitoring Feb 20, 2026, 04:57 PM UTC
Upon further review, an additional fix is still required and in the process of being deployed. Automatic filter syncing may only work intermittently at this point; we'll continue to monitor the situation until the issue is fully resolved.
-
identified Feb 20, 2026, 05:06 PM UTC
ES Filters may not have been synced during the last 30 minutes; we have identified the cause and we are in the process of deploying another fix. Apologies for the inconvenience; we appreciate your patience while we resolve this issue.
-
monitoring Feb 20, 2026, 06:29 PM UTC
The issue may have been resolved after the latest fix was deployed. We'll continue to monitor the situation and we are hopeful the incident can be resolved soon.
-
resolved Feb 20, 2026, 06:42 PM UTC
The issue has been resolved, after verifying that ES filter syncing is now working as expected. Apologies for the inconvenience, and thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jan 21, 2026, 09:30 AM UTC
- Resolved
- Jan 21, 2026, 01:43 PM UTC
- Duration
- 4h 13m
Affected: ScriptRunner for Jira Cloud
Timeline · 3 updates
-
identified Jan 21, 2026, 09:30 AM UTC
We have identified an issue affecting ScriptRunner for Jira Cloud post functions, where some customers are unable to access their post functions.
-
monitoring Jan 21, 2026, 10:49 AM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Jan 21, 2026, 01:43 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 14, 2026, 04:21 PM UTC
- Resolved
- Jan 14, 2026, 04:59 PM UTC
- Duration
- 38m
Affected: ScriptRunner for Jira CloudEnhanced Search for Jira CloudScriptRunner for Confluence Cloud
Timeline · 3 updates
-
identified Jan 14, 2026, 04:21 PM UTC
We have identified the issue and working on resolving the issue asap.
-
monitoring Jan 14, 2026, 04:33 PM UTC
We have updated the task count to help resolve the issue, we are monitering the metrics to check if the incident is resolved.
-
resolved Jan 14, 2026, 04:59 PM UTC
We have rolled back the changes, the incident is resolved now.
Read the full incident report →
- Detected by Pingoru
- Jan 09, 2026, 09:23 AM UTC
- Resolved
- Jan 09, 2026, 10:52 AM UTC
- Duration
- 1h 29m
Affected: ScriptRunner for Jira Cloud
Timeline · 3 updates
-
investigating Jan 09, 2026, 09:23 AM UTC
We are experiencing issues processing sprint and board events from Jira, meaning automated workloads relating to sprints and boards may be failing. We are investigating the issue and will provide more updates soon.
-
monitoring Jan 09, 2026, 09:56 AM UTC
We have reversed a change that we believe to be cause of the problem. The errors that we were witnessing before have stopped since then. We also believe this issue only affected a very small number of clients. We will continue to monitor the situation closely.
-
resolved Jan 09, 2026, 10:52 AM UTC
We are confident that the issue we witnessed this morning is resolved and did not impact the vast majority of our users. We will close this incident, but will continue to monitor the status of the relevant systems as necessary.
Read the full incident report →
- Detected by Pingoru
- Jan 09, 2026, 09:22 AM UTC
- Resolved
- Jan 08, 2026, 10:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jan 09, 2026, 09:22 AM UTC
We experienced delays in automated filter syncing for ScriptRunner for Jira Enhanced Search customers in the US from 19:57 UTC to 22:00 UTC. Some filter results may have been out of date during this period for some customers. A work around was available at this time by manually syncing the filter from the Enhanced Search page. We apologise for the disruption and are implementing architecture changes to improve the stability of this service.
Read the full incident report →
- Detected by Pingoru
- Dec 31, 2025, 07:56 AM UTC
- Resolved
- Dec 31, 2025, 01:14 PM UTC
- Duration
- 5h 18m
Affected: ScriptRunner for Jira CloudScriptRunner for Confluence Cloud
Timeline · 3 updates
-
investigating Dec 31, 2025, 07:56 AM UTC
We are investigating an active issue in the US region where some customer scripts may fail to execute or experience delays due to a problem in our script execution service.
-
monitoring Dec 31, 2025, 08:45 AM UTC
We have identified the issue related to script executions, applied the fix and we are monitoring the services.
-
resolved Dec 31, 2025, 01:14 PM UTC
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.
Read the full incident report →
- Detected by Pingoru
- Dec 29, 2025, 12:30 PM UTC
- Resolved
- Dec 31, 2025, 03:10 PM UTC
- Duration
- 2d 2h
Affected: ScriptRunner for Jira CloudScriptRunner for Confluence Cloud
Timeline · 4 updates
-
investigating Dec 30, 2025, 09:54 AM UTC
A minority of customer scripts didn't run in the US region. This occurred between 12:30 and 16:30 on 29th December.
-
identified Dec 30, 2025, 09:58 AM UTC
We have identified the issue and we are deploying a patch
-
monitoring Dec 30, 2025, 12:33 PM UTC
All scripts are now running as normal. We've implemented a fix that improves our fallback behaviour in the distributed cache system.
-
resolved Dec 31, 2025, 03:10 PM UTC
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. Apologies for the inconvenience
Read the full incident report →
- Detected by Pingoru
- Dec 12, 2025, 04:55 PM UTC
- Resolved
- Dec 16, 2025, 02:28 PM UTC
- Duration
- 3d 21h
Affected: ScriptRunner for Jira Cloud
Timeline · 3 updates
-
investigating Dec 12, 2025, 04:55 PM UTC
Automated migrations of ScriptRunner config via JCMA may be bocked due to JCMA not discovering that ScriptRunner for Jira Cloud has an automated migration path.
-
monitoring Dec 15, 2025, 02:17 PM UTC
After some updates, we have observed the automated path for JCMA migrations to have returned. We are still monitoring the situation and working with Atlassian to ensure it is resolved across the board.
-
resolved Dec 16, 2025, 02:28 PM UTC
We have confirmed that automated migrations are working properly. We have identified the root cause and putting things in place to prevent a future outage.
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 04:48 PM UTC
- Resolved
- Dec 11, 2025, 09:52 AM UTC
- Duration
- 17h 4m
Affected: ScriptRunner for Jira Cloud
Timeline · 3 updates
-
identified Dec 10, 2025, 04:48 PM UTC
W've become aware of delays in script executions and are deploying a measure that should improve matters. We'll monitor its efficacy and update further.
-
identified Dec 10, 2025, 07:58 PM UTC
The measures we deployed to address delays in script execution have been effective, and scripts are now running at normal performance levels. We will continue to monitor the application, and will mark this incident as resolved if no further issues are observed.
-
resolved Dec 11, 2025, 09:52 AM UTC
Scripts appear to have continued to perform at their standard level throughout a period of monitoring, therefore we're marking this incident as resolved. Apologies for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Dec 10, 2025, 11:29 AM UTC
- Resolved
- Dec 11, 2025, 07:44 AM UTC
- Duration
- 20h 15m
Affected: ScriptRunner for Jira Cloud
Timeline · 2 updates
-
identified Dec 10, 2025, 11:29 AM UTC
We have identified the cause of the issue with Scripted Fields not displaying. 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. We apologise for any inconvenience caused.
-
resolved Dec 11, 2025, 07:44 AM UTC
We deployed a fix on 10 Dec at 19:32 UTC to resolve the issue and can confirm that the incident is now fully resolved. We apologise for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Dec 03, 2025, 05:00 PM UTC
- Resolved
- Dec 04, 2025, 05:50 PM UTC
- Duration
- 1d
Affected: ScriptRunner for Jira Cloud
Timeline · 4 updates
-
investigating Dec 03, 2025, 04:08 PM UTC
ScriptRunner scripts using Saved Scripts from Script Manager are experiencing failures to download the Saved Scripts resulting in failures to run the script. It affects ScriptRunner config importing Saved Scripts as well as config pointing directly to saved scripts.
-
identified Dec 04, 2025, 10:49 AM UTC
We have identified an issue with the access to Saved Scripts from the execution environment
-
monitoring Dec 04, 2025, 10:53 AM UTC
We have deployed a fix to the scripts execution process to allow for more robust access to the Saved Scripts from the execution environment.
-
resolved Dec 05, 2025, 11:45 AM UTC
All script using saved scripts from Script Manager are now working as expected.
Read the full incident report →
