解像度の問題のキャッシュは、スクリプトの実行回数が少ない影響を受けました
Issues軽微なインシデント
- resolved
2026年8月27日に9:01am UTCと9:59am UTCの間で実行できなかった小さなスクリプトの数。 問題は解決され、スクリプトは正常に実行する必要があります。 これは、JiraとConfluence CloudのScriptRunnerに影響しました。 不便をおかけします.
公式のインシデント更新を自動翻訳しています。
58 Adaptavist Cloud Apps incidents · 2025年6月 — official updates, affected components, duration and resolution details.
2026年8月27日に9:01am UTCと9:59am UTCの間で実行できなかった小さなスクリプトの数。 問題は解決され、スクリプトは正常に実行する必要があります。 これは、JiraとConfluence CloudのScriptRunnerに影響しました。 不便をおかけします.
公式のインシデント更新を自動翻訳しています。
リスナーやワークフローのスクリプト実行遅延を特定しました。 ソリューションは実装されており、イベントをゆっくりと処理し、遅延スクリプトを実行しています。 これは、JiraクラウドとConfluenceクラウド用のScriptRunnerに影響を与えます
スクリプトの実行リクエストを再び処理し始める環境をパッチ化しました。 スクリプトの実行は正常に戻ります.
ScriptRunner Cloud の問題が解決されていると確信しています。そのため、このインシデントを閉鎖しています。 ご不明な点がございましたら、弊社までお問い合わせください.
公式のインシデント更新を自動翻訳しています。
10:15と10:30 UTCの間、Jira CloudまたはEnhanced SearchアプリのScriptRunnerを使用しての顧客は、Jira REST APIをスクリプト、その他の自動化、JQL検索からアクセスする際に増加率制限が発生することがあります。 これは、個々のユーザーとして行われた要求のアトラスシアンの新しい認証メカニズムの段階的なリリースによって引き起こされました。 変更をロールバックし、あらゆる混乱を招く.
公式のインシデント更新を自動翻訳しています。
ワークフローがドラフトモードの場合、ScriptRunner 条件とバリデータが Jira ワークフロー画面にロードされない問題を修正しました。 ワークアラウンド ユーザーが ScriptRunner ワークフロー 管理者 ページで条件とバリデーターを編集できます。 不便をおかけしますが、
問題は、レガシーワークフローページの廃止によって引き起こされます https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/Final-notice-old-workflow-editor-deprecation-in-July-2026/ba-p/3247499 ユーザーが自分の条件やバリデータを編集するためには、上記の手順に従う必要があります。新しいワークフローエディタは、 ScriptRunner Workflows Admin Page を使用して、条件とバリデータを作成したり、編集したりします。 お問い合わせ!
公式のインシデント更新を自動翻訳しています。
問題が特定され、修正が実装されています.
修正を実装し、結果を監視しています.
この事件は解決しました.
公式のインシデント更新を自動翻訳しています。
ScriptRunner のマイグレーションを DC から Cloud に失敗させる問題を特定しました。 現在、修正を解除し、問題が解決したら別のアップデートを提供します。 修正がリリースされるまで、クラウドへの移行が失敗するまではマイグレーションが開始されていないことをお勧めします.
失敗スクリプトランナーのマイグレーションを解決するために修正が実装されており、現在、システムを監視して安定性を確保しています。 クラウド移行を開始できるようになりました。 ScriptRunner Cloudマイグレーションで問題が発生した場合は、当社のチームでサポートチケットを上げてください.
ScriptRunner クラウドマイグレーションは正常に動作します。 根本的な問題が解決し、継続的な安定性を確保するためにシステムを監視しています。 ありがとうございます.
公式のインシデント更新を自動翻訳しています。
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.