Automation rule beeing triggerd way too late? (8h+ later)

[J B]

Hello, I've encountered some strange behavior. We have an automation rule that changes the issue status to 'Assigned' once a assignee is set. But on one of our issues, this rule is triggered about 8 hours after (and fails, state transition not possible anymore)

On this specific issue other rules also act strange, triggered way too late...

How is this possible? Is there a way to check if the automation is initiated at all, but perhaps nothing done for some reason?

This is the history of the issue: Assignee is set 18 March, 11:41 AM.

But the first trigger of this issue is at 20:46? This is the correct issue, SUP-1127. This rule then fails because of the workflow status transitions not possible anymore (the issue is actually closed already, this is correct).

This is the rule:
The trigger is just this, when value changed:

This is another rule that triggers way too late, setting the source. This should be done once the issue is created. Also setting the Organization and SLA Type.

Perhaps an clue are the times. All these 'delayed' automation rules trigger around the same time in the evening, ~20:40 PM

[Florian Bonniec · Accepted solution]

Hi @J B 

This is most likely due to the automation incident of yesterday. Incident is now fixed and here is the last comment about it.

"Resolved - The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway.
We expect these remaining processes to be completed within approximately two hours, if not sooner.
Mar 19, 04:08 UTC"

https://jira-software.status.atlassian.com/ > Automation for JIRA

Regards

[J B]

Ahh I see. Now I've seen it also on other tickets, also around the same time in the evening.

But why would they run automation rules that are already old/not applicable anymore? I can think of some cases that is useful, but why risk screwing things even more? Issue states getting messed up etc...?

[Florian Bonniec]

I think they just keep all the event in queue, when automation got fixed, it processed all the even in the queue. 

[Arkadiusz Wroblewski]

Hello@J B 

It must be Strongly Related to Incident Yesterday