- Detected by Pingoru
- Nov 25, 2025, 10:03 PM UTC
- Resolved
- Nov 26, 2025, 03:32 AM UTC
- Duration
- 5h 28m
Timeline · 5 updates
-
investigating Nov 25, 2025, 10:03 PM UTC
We’ve identified an issue affecting the Script Listeners and Workflows service. Our team is currently investigating the cause and working to resolve it. We’ll provide an update as soon as we have more information.
-
investigating Nov 25, 2025, 10:06 PM UTC
We have identified that this issue affects only the US region. We are continuing to investigate further and will provide an update as soon as we have more information.
-
investigating Nov 26, 2025, 12:41 AM UTC
We’ve identified the issue and are working on a fix.
-
investigating Nov 26, 2025, 02:23 AM UTC
We found the issue, deployed a fix, and are continuing to monitor the situation.
-
resolved Nov 26, 2025, 03:32 AM 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
- Nov 21, 2025, 08:27 AM UTC
- Resolved
- Nov 21, 2025, 11:15 AM UTC
- Duration
- 2h 48m
Affected: ScriptRunner for Jira CloudScriptRunner for Confluence Cloud
Timeline · 3 updates
-
investigating Nov 21, 2025, 08:27 AM UTC
We have an identified an issue with the Workflows service which is causing this page not to load. 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 Nov 21, 2025, 09:00 AM UTC
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.
-
resolved Nov 21, 2025, 11:15 AM UTC
Our monitoring has now confirmed that the incident has been resolved and that all services are running as normal again. We apologise for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Nov 19, 2025, 03:59 PM UTC
- Resolved
- Nov 20, 2025, 11:15 AM UTC
- Duration
- 19h 15m
Affected: ScriptRunner for Jira CloudBehaviours - ScriptRunner for Jira CloudEnhanced Search for Jira CloudScriptRunner for Confluence Cloud
Timeline · 6 updates
-
investigating Nov 19, 2025, 03:59 PM UTC
We have received reports that the Script Runner portal is failing to load. We are currently investigating
-
monitoring Nov 19, 2025, 04:41 PM UTC
We have implemented a fix and the portal should now load as expected. We will continue to monitor the situation
-
monitoring Nov 19, 2025, 05:26 PM UTC
We are continuing to monitor the situation.
-
monitoring Nov 19, 2025, 08:54 PM UTC
We are continuing to monitor the situation to see if it remains stable.
-
monitoring Nov 20, 2025, 09:11 AM UTC
We are continuing to monitor system health after yesterday's issues with using the ScriptRunner Cloud applications. We will post further updates here when we are confident that the issues have been resolved.
-
resolved Nov 20, 2025, 11:15 AM UTC
We are confident that the issues experienced with using ScriptRunner Cloud apps yesterday are now resolved, so we are closing this incident. If you experience any further issues then please get in touch with our team.
Read the full incident report →
- Detected by Pingoru
- Nov 13, 2025, 07:29 AM UTC
- Resolved
- Nov 13, 2025, 08:58 AM UTC
- Duration
- 1h 29m
Affected: Behaviours - ScriptRunner for Jira Cloud
Timeline · 3 updates
-
investigating Nov 13, 2025, 07:29 AM UTC
We've identified an issue with customers not being able to view their behaviours logs
-
monitoring Nov 13, 2025, 08:21 AM UTC
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.
-
resolved Nov 13, 2025, 08:58 AM UTC
Our monitoring has now confirmed that the incident has been resolved and that all services are running as normal again. We apologise for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Nov 10, 2025, 08:54 AM UTC
- Resolved
- Nov 10, 2025, 09:03 AM UTC
- Duration
- 8m
Affected: ScriptRunner for Jira CloudScriptRunner for Confluence Cloud
Timeline · 2 updates
-
identified Nov 10, 2025, 08:54 AM UTC
We have identified the issue relating to timeouts occuring on a limited number of script executions
-
resolved Nov 10, 2025, 09:03 AM UTC
We have reverted the change causing the shorter timeouts. This has been confirmed to fix the issue.
Read the full incident report →
- Detected by Pingoru
- Oct 22, 2025, 03:33 PM UTC
- Resolved
- Oct 22, 2025, 10:21 PM UTC
- Duration
- 6h 48m
Affected: ScriptRunner for Confluence Cloud
Timeline · 3 updates
-
investigating Oct 22, 2025, 03:33 PM UTC
We have identified an issue with the Script Listener service that is related to an incident with Atlassian's Confluence Webhooks not being delivered. Due to this degradation in the delivery of Webhooks, Script Listeners may not be triggered as a result of this. We are currently monitoring the incident and will post a further update here once we have more information. We apologize for any inconvenience caused.
-
identified Oct 22, 2025, 09:45 PM UTC
Atlassian has identified the issue causing Confluence webhooks to not be delivered and is testing a fix internally.
-
resolved Oct 22, 2025, 10:21 PM UTC
Atlassian has deployed a fix to mitigate the webhooks problem, and we've verified that the Script Listener service is now operating normally. If your Script Listener did not work between 01:00 and 20:47 UTC on October 22, 2025, it was likely affected by this incident.
Read the full incident report →
- Detected by Pingoru
- Oct 21, 2025, 07:24 AM UTC
- Resolved
- Oct 21, 2025, 07:24 AM UTC
- Duration
- —
Affected: ScriptRunner for Jira CloudBehaviours - ScriptRunner for Jira CloudEnhanced Search for Jira CloudScriptRunner for Confluence Cloud
Timeline · 1 update
Read the full incident report →
- Detected by Pingoru
- Oct 02, 2025, 01:20 PM UTC
- Resolved
- Sep 29, 2025, 09:30 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Oct 02, 2025, 01:20 PM UTC
Between 2025-09-29 22:24 UTC and 2025-09-30 00:39 UTC in our US hosting region only the following apps were unable to store and process webhooks, postfunctions and JCMA migration events sent to us from Atlassian due to an AWS service outage: ScriptRunner for Jira Cloud, ScriptRunner for Confluence Cloud and Enhanced Search. This problem impacted Script Listeners, Postfunctions, Scripted Fields that depend on issue updates and Enhanced Search queries using keywords. Apologies for any inconvenience.
Read the full incident report →
Notice September 25, 2025 - Detected by Pingoru
- Sep 25, 2025, 04:00 PM UTC
- Resolved
- Sep 29, 2025, 01:15 PM UTC
- Duration
- 3d 21h
Affected: ScriptRunner for Jira Cloud
Timeline · 3 updates
-
investigating Sep 29, 2025, 09:40 AM UTC
JCMA migrations are not working as expected on ScriptRunenr for Jira Cloud's side and we are not able to complete and report migrations back to JCMA. This results in 0% progress reported for ScriptRunner to customers in Jira DC's JCMA migration status
-
monitoring Sep 29, 2025, 12:00 PM UTC
We have found the root cause of the issue and patched the system. JCMA migrations integration with ScriptRunner is restored. We are monitoring the system to confir it remains stable
-
resolved Sep 29, 2025, 01:45 PM UTC
We confirmed our earlier changes solved the problem reliably. The incident is closed and all migrations are operational. Customers who experienced the issue over the last weekend should re-attempt their migrations.
Read the full incident report →
Notice September 22, 2025 - Detected by Pingoru
- Sep 22, 2025, 09:02 AM UTC
- Resolved
- Sep 22, 2025, 02:09 PM UTC
- Duration
- 5h 7m
Affected: ScriptRunner for Jira CloudBehaviours - ScriptRunner for Jira CloudEnhanced Search for Jira Cloud
Timeline · 4 updates
-
investigating Sep 22, 2025, 09:02 AM UTC
We have had reports that our in app documentation links are not working. We are investigating the cause and will update once we have more information. You can still access our documentation at https://docs.adaptavist.com/
-
identified Sep 22, 2025, 09:25 AM UTC
We have identified the issue and are merging a fix to production.
-
identified Sep 22, 2025, 10:09 AM UTC
We have released a fix for Enhanced Search standalone. We are still releasing a fix for ScriptRunner for Jira Cloud.
-
resolved Sep 22, 2025, 02:09 PM UTC
All in app help documentation for ScriptRunner for Jira Cloud is now available again. Therefore this incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 15, 2025, 08:40 AM UTC
- Resolved
- Aug 27, 2025, 04:52 PM UTC
- Duration
- 12d 8h
Affected: Behaviours - ScriptRunner for Jira Cloud
Timeline · 4 updates
-
investigating Aug 15, 2025, 08:40 AM UTC
We have detected occasional failures during behaviours app installations and are currently investigating the cause.
-
identified Aug 15, 2025, 11:57 AM UTC
We have identified the cause of the failure and are working on a fix for the problem.
-
monitoring Aug 19, 2025, 06:27 AM UTC
A patch has been applied, and the intermittent failures with Behaviours installations have been resolved. We are continuing to monitor installations.
-
resolved Aug 27, 2025, 04:52 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2025, 09:52 AM UTC
- Resolved
- Aug 15, 2025, 08:34 AM UTC
- Duration
- 1d 22h
Affected: Behaviours - ScriptRunner for Jira Cloud
Timeline · 3 updates
-
identified Aug 13, 2025, 09:52 AM UTC
We've detected a problem with loading the latest Behavior Logs, which may result in some logs being temporarily unavailable.
-
monitoring Aug 14, 2025, 10:43 AM UTC
Behaviours logs are now loading correctly, and the search is functional. We will continue to closely monitor performance.
-
resolved Aug 15, 2025, 08:34 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2025, 09:27 AM UTC
- Resolved
- Aug 14, 2025, 08:55 AM UTC
- Duration
- 1d 23h
Affected: ScriptRunner for Jira Cloud
Timeline · 4 updates
-
investigating Aug 12, 2025, 09:27 AM UTC
We have noticed intermittent issues triggering scripts from event webhooks. This is currently impacting some Post functions and Script Listeners. We are currently investigating the the issue.
-
identified Aug 12, 2025, 12:56 PM UTC
We have identified an issue in dealing with a high volume of script events. This caused some event executions to be missed as result.
-
monitoring Aug 12, 2025, 12:59 PM UTC
We have applied a change that will allow us to deal with the increased load. We are currently monitoring and the event executions should be operating as expected. If you experience any issues please contact the support team.
-
resolved Aug 14, 2025, 08:55 AM UTC
This incident has been resolved. Script listeners and post functions should be operating normally.
Read the full incident report →
- Detected by Pingoru
- Aug 01, 2025, 12:17 PM UTC
- Resolved
- Jul 18, 2025, 04:00 PM UTC
- Duration
- —
Timeline · 1 update
-
resolved Aug 01, 2025, 12:17 PM UTC
We identified a bug were customers were unable to perform a JQL Keywords sync between 18th July 17:00 UTC and 28th July 12:30 UTC. A JQL Keywords sync is typically only performed once following the installation of the Enhanced Search app and is unrelated to ongoing filter syncing. We have since fixed the issue and apologise for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Aug 01, 2025, 11:37 AM UTC
- Resolved
- Aug 04, 2025, 11:07 AM UTC
- Duration
- 2d 23h
Affected: Behaviours - ScriptRunner for Jira Cloud
Timeline · 4 updates
-
investigating Aug 01, 2025, 11:37 AM UTC
Behaviours admin management not working. We are currently investigating the cause of the issue. Behaviours will still continue to execute, this incident only affects the ability to manage behaviours via the admin page.
-
identified Aug 01, 2025, 01:50 PM UTC
We identified an issue affecting a platform dependency used by our application, which caused errors in certain API interactions.
-
monitoring Aug 01, 2025, 01:51 PM UTC
The issue is no longer occurring, and systems are operating normally. We are continuing to monitor and investigate the root cause.
-
resolved Aug 04, 2025, 11:07 AM UTC
This incident has been fully resolved. The root cause was an issue with Atlassian Forge infrastructure that affected some customers' ability to manage behaviours through the admin page. All systems are now operating normally. If you continue to experience any issues with behaviour management, please contact support. Sorry for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Jul 30, 2025, 11:40 AM UTC
- Resolved
- Jul 30, 2025, 01:57 PM UTC
- Duration
- 2h 17m
Affected: ScriptRunner for Jira CloudEnhanced Search for Jira CloudScriptRunner for Confluence Cloud
Timeline · 6 updates
-
identified Jul 30, 2025, 11:40 AM UTC
A number of proxy requests in US are failing due to an issue with infrastructure
-
identified Jul 30, 2025, 11:54 AM UTC
This incident also affects EU customers.
-
monitoring Jul 30, 2025, 12:13 PM UTC
We increased our infrastructure resources and we are monitoring
-
monitoring Jul 30, 2025, 12:30 PM UTC
We are still actively monitoring the situation and deploying another potential fix to further improve the health of the underlying infrastructure.
-
monitoring Jul 30, 2025, 12:42 PM UTC
We believe that the issues with the underlying infrastructure are now fixed. We will continue to monitor the situation until we are confident that the issue is permanently resolved.
-
resolved Jul 30, 2025, 01:57 PM UTC
Rolling back the affected service fixed the issue. Number of healthy requests is back to the expected levels. Sorry for any inconvenience caused.
Read the full incident report →
- Detected by Pingoru
- Jul 25, 2025, 09:44 AM UTC
- Resolved
- Jul 28, 2025, 08:47 AM UTC
- Duration
- 2d 23h
Affected: ScriptRunner for Jira CloudEnhanced Search for Jira Cloud
Timeline · 4 updates
-
investigating Jul 25, 2025, 09:44 AM UTC
ScriptRunner and Enhanced Search are not laoding on customer instances and customers cannot access the user interfaces. This affects the UI but background processes like Script Listeners, Post Functions, and fylter syncing continue to work normally.
-
identified Jul 25, 2025, 11:10 AM UTC
We have identified the issue, and we are working on rolling out a fix. Affected customers are still not able to access ScriptRunner's user interface but background scripts are working as expected.
-
monitoring Jul 25, 2025, 11:54 AM UTC
We have a new minor version upgrade of the app rolling out via Atlassian's Marketplace and affected customers should see the issue automatically rectifying. If you require access to ScriptRunner urgently you can expedite the update by navigating to Apps -> Manage Apps and clicking the update button on the ScriptRunner listing.
-
resolved Jul 28, 2025, 08:47 AM UTC
ScriptRunner user interface is loading as expected for all customers after an update was rolled out starting on Friday July 25th.
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2025, 10:18 AM UTC
- Resolved
- Jul 16, 2025, 07:28 PM UTC
- Duration
- 9h 9m
Affected: Enhanced Search for Jira Cloud
Timeline · 2 updates
-
identified Jul 16, 2025, 10:18 AM UTC
We are currently experiencing delays in syncing issue properties meaning some filter results may be out of date since Friday 11th July. We know the issue and are working on clearing the queue.
-
resolved Jul 16, 2025, 07:28 PM UTC
The backlog of events has now been processed and filter results should be accurate again. Thank you for your patience.
Read the full incident report →
- Detected by Pingoru
- Jul 10, 2025, 02:33 PM UTC
- Resolved
- Jul 18, 2025, 08:17 AM UTC
- Duration
- 7d 17h
Affected: ScriptRunner for Jira Cloud
Timeline · 13 updates
Read the full incident report →
- Detected by Pingoru
- Jul 09, 2025, 07:54 AM UTC
- Resolved
- Jul 09, 2025, 07:54 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Jul 09, 2025, 07:54 AM UTC
We discovered that filters containing only linkedIssuesOf without any other Enhanced Search functions were not syncing following a region migration. These filters could still be synced manually, and they displayed the correct results when performing a search in the UI. If any affected filters had their JQL or name updated, they resumed syncing as usual. All other filters, including those containing linkedIssuesOf alongside other Enhanced Search functions, continued syncing correctly after a region migration. For example: This filter containing only linkedIssuesOf was not syncing: issueFunction in linkedIssuesOf("issue=ES1") But this filter containing linkedIssuesOf and another Enhanced Search function was syncing: issueFunction in linkedIssuesOf("issue=ES1") and issueFunction in childrenOf("project=Enhanced-Search") We have corrected this issue, and any affected filters should now be syncing correctly. No further action is required.
Read the full incident report →
- Detected by Pingoru
- Jun 20, 2025, 04:16 PM UTC
- Resolved
- Jun 20, 2025, 04:16 PM UTC
- Duration
- —
Affected: ScriptRunner Connect
Timeline · 1 update
-
resolved Jun 20, 2025, 04:16 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 20, 2025, 03:39 PM UTC
- Resolved
- Jun 20, 2025, 04:12 PM UTC
- Duration
- 33m
Affected: Enhanced Search for Jira Cloud
Timeline · 3 updates
-
identified Jun 20, 2025, 03:39 PM UTC
Potential fix has been identified; working on a solution at this moment.
-
monitoring Jun 20, 2025, 04:06 PM UTC
Potential fix is being deployed; currently monitoring the situation.
-
resolved Jun 20, 2025, 04:12 PM UTC
Fix has been deployed and filter synchronisation in Enhanced Search is working as expected again.
Read the full incident report →
- Detected by Pingoru
- Jun 19, 2025, 01:41 PM UTC
- Resolved
- Jun 19, 2025, 02:17 PM UTC
- Duration
- 35m
Affected: ScriptRunner for Jira CloudScriptRunner for Confluence Cloud
Timeline · 3 updates
-
identified Jun 19, 2025, 01:41 PM UTC
We have identified a bug with the latest changes we released. The bug prevents the app from fetching settings and workflow conditions. We are rolling back the changes now.
-
monitoring Jun 19, 2025, 01:57 PM UTC
We have rolled back the broken changes, systems look operational and the errors have stopped now.
-
resolved Jun 19, 2025, 02:17 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 09:39 AM UTC
- Resolved
- Jun 23, 2025, 07:45 PM UTC
- Duration
- 11d 10h
Affected: Behaviours - ScriptRunner for Jira Cloud
Timeline · 6 updates
-
investigating Jun 12, 2025, 09:39 AM UTC
Behaviours logs are failing to load, we are currently investigating the underlying cause.
-
identified Jun 13, 2025, 09:28 AM UTC
We have determined that there is an issue with a search index on a specific day, resulting in the inability to retrieve all behavior logs.
-
monitoring Jun 16, 2025, 03:47 PM UTC
We have patched the issue, and behaviours logs are loading. We will continue to monitor the situation.
-
investigating Jun 17, 2025, 07:26 AM UTC
We have identified that some customers' Behaviours logs are failing to load. Our team is currently investigating the issue. We’ll share further updates as we learn more.
-
monitoring Jun 17, 2025, 10:15 AM UTC
We have patched the issue by reducing the Behaviours logs being fetched down to the past 6 days. We will continue to monitor this issue.
-
resolved Jun 23, 2025, 07:45 PM UTC
The Behaviours log search functionality has been restored and is currently operating stably. As part of the resolution, a patch was implemented to limit search queries to the most recent seven days, which has improved reliability under load.
Read the full incident report →
