Atlassian Developer incident
Small percentage of Errors in Forge Runtime in EU Central (Europe) and CA Central (Canada)
Atlassian Developer experienced a minor incident on May 14, 2025 affecting Forge Function Invocation, lasting 5d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 14, 2025, 12:03 AM UTC
We are aware of some users experiencing a low percentage of Forge invocation errors in their apps in EU Central and CA Central regions. Our team is investigating this with urgency and an update will be provided when available.
- identified May 14, 2025, 03:38 AM UTC
Our team has identified the cause of this issue and is working towards a resolution. If you are experiencing Forge invocations 'unhandled exception error' in the Developer Console, please re-deploy your apps which should rectify the issue in the meantime.
- identified May 14, 2025, 08:31 AM UTC
We are working on the fix. We are currently redeploying the apps which had the error. In the meantime if you are experiencing Forge invocations 'unhandled exception error' in the Developer Console, please re-deploy your apps which should rectify the issue.
- monitoring May 14, 2025, 11:16 AM UTC
The apps which had the error were redeployed by the team. We will monitor if we observe any issues for them. In case you are still experiencing Forge invocations 'unhandled exception error' in the Developer Console, please re-deploy your apps which would rectify the issue.
- monitoring May 14, 2025, 01:04 PM UTC
We identified 38 app deployments which might still be affected with the issue (intermittent invocation failures). These would be redeployed in next 24hours. No new app deployments should be affected by the issue. Next update ~5AM UTC
- monitoring May 15, 2025, 05:20 AM UTC
The majority of app re-deployments have been completed and intermittent invocation errors should now be mitigated. Our team continues to work with our service provider on the small percentage of remaining apps and we will update once this issue has been resolved.
- resolved May 19, 2025, 01:11 AM UTC
The root cause of this issue with our service provider has now been resolved and this should no longer be impacting any customers.