We had a bug JIRAAUTOSERVER-380 as data for issue deleted trigger was loaded lazily and if this data is lost before rule completes it always had failed with an error, this was fixed in a4j v7.4.1. Now the rule works fine if the "delay execution" checkbox is not checked for subsequent action.

Rule is being set up like -> If the issue deleted event rule is triggered then A) send web request to get an access token from Azure with a delay execution of subsequent rules checked
and B ) send web request to get/post issue data (Screenshot attached).
The above rule fails with no issue key error (error attached). This seems to happen due to the cache getting updated post the first web request is sent and since the delay is checked, the subsequent send web request fails. If we do not delay subsequent rules, the automation rule works fine.

As the access token has expiry, we would like the issue data to be present in cache when the issue deleted event is triggered till the automation rule completes, when there is a delay execution checked.