58 Adaptavist Cloud Apps incidents · giugno 2025 — official updates, affected components, duration and resolution details.
Un piccolo numero di script non è riuscito a funzionare tra 9:01am UTC e 9:59am UTC il 27 agosto 2026. Il problema è ora risolto e gli script dovrebbero essere in esecuzione normalmente. Questo ha interessato ScriptRunner per Jira e Confluence Cloud. Chiedo scusa per qualsiasi inconveniente causato.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Abbiamo identificato i ritardi di esecuzione degli script per gli ascoltatori e i flussi di lavoro. La soluzione è stata implementata e stiamo lentamente elaborando gli eventi e quindi eseguendo gli script ritardati. Questo colpisce ScriptRunner per Jira Cloud e Confluence Cloud
Abbiamo patchato l'ambiente per avviare l'elaborazione delle richieste di esecuzione degli script di nuovo. Le esecuzioni degli script sono di nuovo normali.
Siamo sicuri che i problemi ScriptRunner Cloud sono ora risolti, quindi stiamo chiudendo questo incidente. Se si verificano ulteriori problemi, si prega di contattare il nostro team.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Tra le 10:15 e le 10:30 UTC, i clienti che utilizzano ScriptRunner per le applicazioni di Jira Cloud o Enhanced Search possono aver sperimentato un aumento della velocità di limitazione quando si accede alle API di Jira REST dai loro script, altre automazioni o ricerche JQL. Ciò è stato causato da un graduale rilascio del nuovo meccanismo di autenticazione di Atlassian per richieste fatte come singoli utenti. Abbiamo rimboccato i cambiamenti e ci scusiamo per qualsiasi disturbo.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Abbiamo identificato un problema in cui le condizioni e i validatori di ScriptRunner non riescono a caricare sullo schermo dei flussi di lavoro Jira quando il flusso di lavoro è in modalità abbozzo Come utenti di workaround possono modificare le loro condizioni e validatori tramite la pagina di amministrazione dei flussi di lavoro ScriptRunner Le scuse per qualsiasi inconveniente causato
Il problema è causato dalla deprecazione della pagina dei flussi di lavoro legacy https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Final-notice-old-workflow-editor-deprecation-in-luglio-2026/ba-p/3247499 Per gli utenti di modificare le loro condizioni e validatori dovranno seguire le istruzioni di cui sopra per utilizzare la nuova esperienza dell'editor del flusso di lavoro o modificare le loro condizioni e validatori tramite la pagina Grazie!
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Il problema è stato identificato e si sta attuando una correzione.
Una soluzione è stata implementata e stiamo monitorando i risultati.
Questo incidente è stato risolto.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Abbiamo identificato un problema che sta causando le migrazioni di ScriptRunner da DC a Cloud per fallire. Attualmente stiamo lavorando per rilasciare una correzione e forniremo un altro aggiornamento una volta risolto il problema. Noi consigliamo che le migrazioni non vengono avviate fino a quando non abbiamo confermato che la correzione viene rilasciata, in quanto eventuali migrazioni a Cloud attualmente falliranno.
Una correzione è stata implementata per risolvere le migrazioni ScriptRunner inadeguate, e stiamo monitorando il sistema per garantire la stabilità. Le migrazioni cloud possono ora essere avviate. Se si incontrano ulteriori problemi con la migrazione ScriptRunner Cloud, si prega di alzare un biglietto di supporto con il nostro team.
Le migrazioni ScriptRunner Cloud funzionano normalmente. Il problema di fondo è stato affrontato e stiamo monitorando il sistema per garantire una stabilità continua. Grazie per la pazienza.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
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.