Scheduled 5 min-triggers not firing for some Apps
Incident
Report for Atlassian Developer
Resolved
On Aug 25th, 2026, between 08:12 UTC and 11:03 UTC, some Marketplace apps may have experienced scheduled triggers (5-minute intervals) not firing as expected.
The issue has now been resolved and the 5-minute scheduled triggers are operating normally for all customers.
The issue has now been resolved and the 5-minute scheduled triggers are operating normally for all customers.
Monitoring
A fix has been successfully deployed for the issue affecting scheduled triggers (5-minute intervals) for some Marketplace apps. We continue to monitor the situation and should be fully recovered soon.
We should be able to provide more updates in the one hour.
We should be able to provide more updates in the one hour.
This incident affected: APIs (Bitbucket Cloud APIs, Confluence Cloud APIs, Jira Cloud APIs, Product Events, User APIs, Webhooks, Web Triggers), Marketplace (App listing management, App listings, App pricing, App submissions, Category landing pages, Evaluations and purchases, In-product Marketplace and app installation (Cloud), In-product Marketplace and app installation (Server), Notifications, Private listings, Reporting APIs and dashboards, Search, Vendor management, Vendor Home Page), Developer (App Deployment, Artifactory (Maven repository), Create and manage apps, Developer documentation, Forge App Installation, Forge CDN (Custom UI), Forge Function Invocation, aui-cdn.atlassian.com, Forge App Logs, Forge App Monitoring, Developer console, Forge direct app distribution, Hosted storage, Forge CLI, End-user consent, Forge App Alerts, App Data Residency, Forge SQL, Forge Monetisation, Forge Feature Flags Evaluations, Forge Object Store), Support (Atlassian Support contact form, Developer community, Developer service desk, Marketplace service desk, Atlassian Support, Vulnerability management [AMS]), and Authentication and user management.