58 Adaptavist Cloud Apps incidents · Juni 2025 — official updates, affected components, duration and resolution details.
Eine kleine Anzahl von Skripten lief nicht zwischen 9:01 Uhr UTC und 9:59 Uhr UTC am 27. August 2026. Das Problem ist nun behoben und Skripte sollten normal laufen. Dies betraf ScriptRunner für Jira und Confluence Cloud. Entschuldigung für jede verursachte Unannehmlichkeit.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Wir haben Verzögerungen bei der Ausführung von Skripten für Listener und Workflows identifiziert. Die Lösung wurde implementiert und wir verarbeiten die Ereignisse langsam und führen daher die verzögerten Skripte aus. Dies betrifft ScriptRunner für Jira Cloud und Confluence Cloud
Wir haben die Umgebung gepatcht, um die Verarbeitung von Skriptausführungsanforderungen erneut zu starten. Script-Ausführungen sind wieder normal.
Wir sind zuversichtlich, dass die ScriptRunner Cloud-Probleme jetzt behoben sind, daher schließen wir diesen Vorfall ab. Wenn Sie weitere Probleme haben, kontaktieren Sie bitte unser Team.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Zwischen 10:15 und 10:30 UTC können Kunden, die ScriptRunner für Jira Cloud- oder Enhanced Search-Apps verwenden, beim Zugriff auf Jira REST-APIs aus ihren Skripten, anderen Automatisierungen oder JQL-Suchen eine erhöhte Ratenbegrenzung erfahren haben. Dies wurde durch eine schrittweise Veröffentlichung des neuen Authentifizierungsmechanismus von Atlassian für Anfragen als einzelne Benutzer verursacht. Wir haben die Änderungen zurückgenommen und uns für jede Störung entschuldigt.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Wir haben ein Problem festgestellt, bei dem ScriptRunner-Bedingungen und Validatoren nicht auf den Jira Workflow-Bildschirm geladen werden können, wenn sich der Workflow im Entwurfsmodus befindet Als Workaround können Benutzer ihre Bedingungen und Validatoren über die ScriptRunner Workflows Admin-Seite bearbeiten. Entschuldigung für eventuelle Unannehmlichkeiten
Das Problem wird durch die Abwertung der Legacy-Workflows-Seite verursacht https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Final-notice-old-workflow-editor-deprecation-in-July-2026/ba-p/3247499 Damit Benutzer ihre Bedingungen und Validatoren bearbeiten können, müssen sie die obigen Anweisungen befolgen, um die neue Workflow-Editor-Erfahrung zu verwenden, oder ihre Bedingungen und Validatoren über die ScriptRunner Workflows Admin-Seite bearbeiten. Danke!
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Das Problem wurde identifiziert und ein Fix wird implementiert.
Ein Fix wurde implementiert und wir überwachen die Ergebnisse.
Dieser Vorfall wurde behoben.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
Wir haben ein Problem identifiziert, das dazu führt, dass ScriptRunner-Migrationen von DC zu Cloud fehlschlagen. Wir arbeiten derzeit an der Veröffentlichung eines Fixes und werden ein weiteres Update bereitstellen, sobald das Problem behoben ist. Wir weisen darauf hin, dass Migrationen erst eingeleitet werden, wenn wir bestätigt haben, dass der Fix veröffentlicht wird, da alle Migrationen in die Cloud derzeit fehlschlagen.
Ein Fix wurde implementiert, um die fehlgeschlagenen ScriptRunner-Migrationen zu beheben, und wir überwachen derzeit das System, um die Stabilität zu gewährleisten. Cloud-Migrationen können nun initiiert werden. Wenn Sie weitere Probleme mit Ihrer ScriptRunner Cloud-Migration haben, sammeln Sie bitte ein Support-Ticket mit unserem Team.
ScriptRunner Cloud-Migrationen funktionieren normal. Das zugrunde liegende Problem wurde angesprochen, und wir überwachen das System, um eine anhaltende Stabilität zu gewährleisten. Vielen Dank für Ihre Geduld.
Automatisch aus der offiziellen Störungsmeldung übersetzt.
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.
A fix has been deployed and affected settings have returned to normal. We will continue to monitor to confirm full resolution.
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.
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.
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.
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.
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.
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.
The issue has been fixed and the fix has been deployed. We are now monitoring the situation.
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.
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
A fix has been implemented and we are monitoring the results.
At 13:21 28th May 2026 to 07:34 29th May 2026 UTC, there was an issue affecting script executions.
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.
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.
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.
Atlassian published an update to their status page that their monitoring confirmed the issue with delays in delivering events is now resolved
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
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.
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.
The solution seems to have mitigated the issues we were seeing this morning. We are continue to monitor the situation closely.
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.
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.
We have identified that some requests within customer scripts failed on 24/03/2026 between 16:27 -> 19:52 UTC
This incident has been resolved.
Macros are currently impacted due to an Atlassian platform incident.
We continue to monitor the Atlassian incident affecting Scriptrunner macros. We will provide updates as more information becomes available.
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
Atlassian has resolved the incident affecting macro functionality. We are monitoring to ensure services is stable.
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.
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.
At 08:25 UTC the execution demand dropped to normal levels and the system resumed normal operation.
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.
At 17:35 the execution demand dropped to normal levels and the system resumed normal operation.