Hello,

I think that once the event is triggered, the whole flow shifts to the child that is subscribing to this event. In other words, the execution is no longer inside the same block.

You could try the following approach:

• Add an input parameter like IsSaving to the event itself
• Move the spinner logic to the child flow that handles the event, meaning inside the action flow of the subscriber
• In the parent (the publisher / the one triggering the event), simply trigger the event and remove both assign actions related to the spinner state

This way, the loading state is handled where the actual processing happens rather than in the publisher flow.