缓存解决问题影响到少量文字处决
Issues轻微事件
- resolved
少量脚本在协调世界时9:01分和2026年8月27日协调世界时9:59分之间未能运行. 现在问题已经解决,脚本应该正常运行. 这影响了为Jira和相交云而作的脚本跑车. 抱歉造成任何不便.
自动翻译自官方事件更新。
58 Adaptavist Cloud Apps incidents · 2025年6月 — official updates, affected components, duration and resolution details.
少量脚本在协调世界时9:01分和2026年8月27日协调世界时9:59分之间未能运行. 现在问题已经解决,脚本应该正常运行. 这影响了为Jira和相交云而作的脚本跑车. 抱歉造成任何不便.
自动翻译自官方事件更新。
我们已经确定了听从者和工作流程的脚本执行延迟。 解决方案已经实施,我们正在缓慢地处理事件,从而执行延迟的脚本。 这影响了 Jira 云和相会云的脚本运行器
我们已经修复了环境, 可以重新开始处理脚本执行请求 。 脚本处决恢复正常.
我们相信史克威尔云问题已经解决, 如果你有任何问题,请联系我们的团队.
自动翻译自官方事件更新。
在协调世界时10:15至10:30之间,使用ScriptRunner为Jira Cloud或增强搜索应用程序的客户在通过脚本,其他自动化或JQL搜索访问Jira REST API时,可能遭遇了更高的收视率限制. 这是由于Atlassian作为个人用户提出的请求的新认证机制逐渐被发布. 我们收回了修改,并对任何干扰表示歉意.
自动翻译自官方事件更新。
我们已经确定一个问题,即当工作流程处于草稿模式时,脚本运行器条件和验证器无法在 Jira Workflows 屏幕上加载 作为绕行的用户可以通过脚本Runner工作流程管理页面编辑其条件和验证器 对造成的不便道歉
这个问题是遗留工作流程页面贬值造成的 https://community.atlassian.com/forums/Jira-Cloud-Admins-articles/最后-通知-老-workflow-editor-depressation-in-July-2026/ba-p/3247499 (中文(简体) ). 用户要编辑自己的条件和验证器,需要遵循上面的指示,通过脚本Runner Workflows Admin Page使用新的工作流程编辑器体验或编辑自己的条件和验证器 谢谢!
自动翻译自官方事件更新。
这一问题已经确定,一个解决办法正在实施之中.
一项措施已经执行,我们正在监测结果.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们发现了一个导致ScriptRunner从DC迁移到Cloud失败的问题。 我们目前正在努力公布一个解决办法,并将在该问题得到解决后提供另一个最新情况。 我们建议,除非我们确认已解冻,否则不会开始迁移,因为目前向云的迁移将失败.
为解决失败的ScriptRunner移民问题,已经实施了一个解决方案,我们正在监测该系统,以确保稳定。 现在可以开始云移了。 如果你在你的斯克普特朗纳云层迁移中再遇到任何问题,请向我们的团队举起支持票.
脚本Runner云迁移正常运行. 根本问题已经得到解决,我们正在监测该制度,以确保持续稳定。 谢谢你的耐心.
自动翻译自官方事件更新。
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.