If there are multiple actions in the queue, the current IAM open action (runActionNamed:) needs to execute first, before other IAMs in the queue. This was not working correctly when using useAsyncDecisionHandlers - the next message from the queue was presented before the chained action was inserted at the front.
This PR fixes that.
Background
If there are multiple actions in the queue, the current IAM open action (
runActionNamed:
) needs to execute first, before other IAMs in the queue. This was not working correctly when usinguseAsyncDecisionHandlers
- the next message from the queue was presented before the chained action was inserted at the front. This PR fixes that.Implementation
Testing steps
Is this change backwards-compatible?