Delay in execution of Automation rules

What to do

• Check whether you use Confluence Confluence Automations. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 27m it lasted.

  Anything that failed between 2025-10-22 06:20 UTC and 2025-10-22 06:47 UTC may need a replay.

• Subscribe to Confluence's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=confluence works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Confluence 3

1. investigatingOct 22, 2025, 6:20 AM UTC

   We understand that our customers are experiencing delay in execution of Automation rules. While our team is investigating further on this, it looks like a follow-on effect of the recent AWS outage. We continue to investigate further on this and we shall keep you informed of the progress every hour if not sooner.

   provider

2. identifiedOct 22, 2025, 6:34 AM UTC

   Atlassian team has identified the cause of the issue that led to delay in execution of Automation rules. This is a follow-on effect of the recent AWS outage. We shall keep you informed of the progress every hour, if not sooner.

   provider

3. resolvedOct 22, 2025, 6:47 AM UTC

   Our teams have identified and fixed the root cause of the issue that caused delay in executing Automation rules. This was caused due to scaling issues following on from the recent AWS outage. This issue is marked as resolved.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.