Deviniti incident

Degraded Performance: Delays in Plugins due to delays in Forge triggers

Minor Resolved View vendor source →

Deviniti experienced a minor incident on May 11, 2026 affecting Extension for JSM and Azure AD Attributes Sync for Jira and 1 more component, lasting 1d 23h. The incident has been resolved; the full update timeline is below.

Started
May 11, 2026, 11:25 AM UTC
Resolved
May 13, 2026, 10:52 AM UTC
Duration
1d 23h
Detected by Pingoru
May 11, 2026, 11:25 AM UTC

Affected components

Extension for JSMAzure AD Attributes Sync for JiraIssue TemplatesRequirements & Test Management for Jira Cloud

Update timeline

  1. identified May 11, 2026, 11:25 AM UTC

    We have identified an issue where Atlassian Forge triggers are experiencing significant processing delays. This directly affects data sync within our apps, causing latencies of several to over fifteen minutes. Our team is in contact with Atlassian support to expedite a resolution. We will provide further updates as they become available.

  2. identified May 11, 2026, 11:31 AM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring May 11, 2026, 12:40 PM UTC

    Atlassian has confirmed that rate limits have been adjusted. However, a significant backlog of 1M+ messages accumulated during the rate limiting period. As the queue processes in order, new events are queued behind the existing backlog - delivery times will improve progressively as the queue drains. Atlassian is actively monitoring the situation and expects full normalization within the next few hours as the queue count is steadily decreasing. We are continuing to work closely with Atlassian to restore full service stability as quickly as possible.

  4. monitoring May 11, 2026, 02:49 PM UTC

    Status of the source incident can be followed on Atlassian statuspage: https://developer.status.atlassian.com/incidents/m54l7lhqs6cp

  5. monitoring May 12, 2026, 07:00 AM UTC

    Although Atlassian has closed the incident on their end and marked it as resolved, we are still observing delays in the delivery of Forge trigger-related events. We have escalated the issue and are actively investigating. We will continue to provide updates here as the situation develops.

  6. monitoring May 12, 2026, 02:17 PM UTC

    Atlassian has updated their statuspage informing about Delay in Jira Webhook Delivery: https://developer.status.atlassian.com/incidents/239w0k720tn3

  7. monitoring May 13, 2026, 07:57 AM UTC

    We are aware that Atlassian is currently experiencing delays with automation triggers, which may also affect our applications. According to Atlassian, their Automation service is the most impacted at this time. We are monitoring the situation closely and will provide updates as more information becomes available. You can follow Atlassian's own incident thread here: https://jira-service-management.status.atlassian.com/incidents/v307yb60q5g7

  8. resolved May 13, 2026, 10:52 AM UTC

    The situation has stabilized and full operational status has been restored. All systems are functioning normally. We apologize for any inconvenience caused and thank you for your patience.