Issue Summary

Jira moved to an eventual consistency model, which causes problems with Automation because when we receive an event from Jira, eg an fields updated event, we look up related data from Jira with the assumption that if the event has been published to us, retrieving from Jira should show us the updated data. 

With eventual consistency, this assumption is no longer true.

 Steps to Reproduce

1. None, it's random

Expected Results

Rules should not randomly fail due to missing Jira data

Actual Results

Rule fails with error "The flow actor doesn't have permission to view the event that triggered this flow", or other generic error.

Workaround

• If the failure is not on the trigger, adding a delay of a few seconds will usually help, however, there is no workaround if the failure is on the trigger. ; or
• If the automation triggered , but it have condition set up within the trigger , move the condition outside the trigger configuration.