58 incidente Adaptavist Cloud Apps înregistrate începând din iunie 2025, cu actualizări oficiale, componente afectate, durată și informații despre rezolvare.
Un număr mic de scenarii nu au reușit să ruleze între 9:01 UTC și 9:59 UTC pe 27 august 2026. Problema este acum rezolvată și scripturile ar trebui să fie difuzate în mod normal. Acest lucru a afectat ScriptRunner pentru Jira și Confluence Cloud. Scuze pentru orice neplăceri cauzate.
Traducere automată din actualizarea oficială a incidentului.
Am identificat întârzieri în execuţia scripturilor pentru ascultători şi fluxuri de lucru. Soluţia a fost implementată şi procesăm încet evenimentele şi, prin urmare, executăm scripturile întârziate. Acest lucru afectează ScriptRunner pentru Jira Cloud și Confluence Cloud
Am patch-uri de mediu pentru a începe procesarea cererilor de executare script din nou. Execuţiile au revenit la normal.
Suntem încrezători că problemele ScriptRunner Cloud sunt acum rezolvate, aşa că închidem acest incident. Dacă aveţi alte probleme, vă rugăm să contactaţi echipa noastră.
Traducere automată din actualizarea oficială a incidentului.
Între 10:15 și 10:30 UTC, clienții care utilizează ScriptRunner pentru Jira Cloud sau aplicații de căutare îmbunătățită ar fi putut experimenta o limitare a ratei la accesarea API-urilor Jira REST din scripturile lor, alte automatizări sau căutări JQL. Acest lucru a fost cauzat de o versiune treptată a noului mecanism de autentificare al Atlassian pentru cererile făcute ca utilizatori individuali. Am întors schimbările şi ne cerem scuze pentru orice întrerupere.
Traducere automată din actualizarea oficială a incidentului.
Am identificat o problemă în care condițiile ScriptRunner și validatorii nu se încarcă pe ecranul Jira Fluxuri de lucru atunci când fluxul de lucru este în modul de proiectare Ca un lucru în jurul utilizatorilor pot edita condițiile lor și validatori prin intermediul ScriptRunner fluxuri de lucru admin pagina Scuze pentru orice neplăceri cauzate
Problema este cauzată de deprecarea paginii fluxurilor de lucru moștenite În conformitate cu articolul 2 alineatul (2) din Regulamentul (CE) nr. Pentru ca utilizatorii să-şi editeze condiţiile şi validatorii va trebui să urmeze instrucţiunile de mai sus pentru a utiliza noua experienţă de editor al fluxului de lucru sau pentru a-şi edita condiţiile şi validatorii prin intermediul paginii ScriptRunner Workflows Admin Mulţumesc!
Traducere automată din actualizarea oficială a incidentului.
Problema a fost identificată și se pune în aplicare o soluție.
A fost implementată o soluţie şi monitorizăm rezultatele.
Acest incident a fost rezolvat.
Traducere automată din actualizarea oficială a incidentului.
Am identificat o problemă care cauzează eşecul migraţiilor ScriptRunner din DC în Cloud. În prezent lucrăm la eliberarea unui fix și vom oferi o altă actualizare după rezolvarea problemei. Vă recomandăm ca migraţiile să nu fie iniţiate până când nu vom confirma că fixarea este eliberată, deoarece orice migraţie către Cloud va eşua în prezent.
A fost implementat un fix pentru rezolvarea migraţiilor eşuate ale ScriptRunner şi în prezent monitorizăm sistemul pentru a asigura stabilitatea. Migraţiile în nori pot fi iniţiate acum. Dacă întâlniți orice alte probleme cu migrarea ScriptRunner Cloud, vă rugăm să ridicați un bilet de sprijin cu echipa noastră.
Migrațiile ScriptRunner Cloud funcționează normal. Problema de bază a fost abordată și monitorizăm sistemul pentru a asigura stabilitatea continuă. Mulţumesc pentru răbdare.
Traducere automată din actualizarea oficială a incidentului.
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.