Atlassian Developer incident

Scheduled Triggers not working for Forge apps

Major Resolved View vendor source →

Atlassian Developer experienced a major incident on February 6, 2026 affecting Forge Function Invocation, lasting 1h 54m. The incident has been resolved; the full update timeline is below.

Started
Feb 06, 2026, 09:37 AM UTC
Resolved
Feb 06, 2026, 11:32 AM UTC
Duration
1h 54m
Detected by Pingoru
Feb 06, 2026, 09:37 AM UTC

Affected components

Forge Function Invocation

Update timeline

  1. investigating Feb 06, 2026, 09:37 AM UTC

    Impact We are currently experiencing an issue affecting the Forge platform, specifically impacting scheduled triggers. Users may notice that these triggers are not executing as expected. This issue was initially observed around 2 AM UTC. Current Status Our engineering team is actively investigating the issue and working toward restoring full service. The team is focused on identifying the root cause and implementing a solution to resolve the incident. Next Steps We will provide a status update in 60 minutes. The restoration of service is our priority, and the team will continue to monitor and address the situation as developments occur.

  2. identified Feb 06, 2026, 10:39 AM UTC

    Impact We are currently experiencing an issue affecting the Forge platform, specifically impacting scheduled triggers. Users may notice that these triggers are not executing as expected. This issue was initially observed around 2 AM UTC. Current Status Our engineering team is actively investigating the issue. The issue is suspected to be related to a recent change that was deployed. The team is currently rolling back the changes. Next Steps We will provide a status update in 60 minutes. The restoration of service is our priority, and the team will continue to monitor and address the situation as developments occur.

  3. resolved Feb 06, 2026, 11:32 AM UTC

    Impact We are currently experiencing an issue affecting the Forge platform, specifically related to scheduled triggers. Users may encounter instances where these triggers are not executing as anticipated, disrupting the normal operation of their Forge apps. This behavior began approximately at 2 AM UTC. Current Status Our engineering team identified the root cause and performed a rollback deployment to resolve the issue.