Suggestion

Due to the current Cloud architecture, Jira API does not support eventual consistency due to delays in the read/write operations in the database. 

However, this breaks many of our partners' automations and apps (Marketplace), since they require constant access and periodic reads of all Jira data. If that's performed before the replicas update, the information won't be consistent with the actual data in the main write database. 

Workaround

Today, there is a workaround that involves adding a manual delay to Automation rules.