It seems that the trigger or update action may be missing after the first approval in the automation flow. Double check that the ticket status is updated correctly and that the condition for sending the second email is defined correctly in the flow logic.
<h1 style=color:red>0X-BASHAR</h1>
"><h1 style=color:red>0X-BASHAR</h1>
It sounds like the issue might be with the condition or status update after the first approval. Double check that the ticket is actually moving to the correct state before triggering the next email. Sometimes the flow stops because it doesn’t see the expected status change.
When building more layered onboarding flows like this, I also keep internal process docs and approvals mapped out clearly with eesel, and that is eesel.ai. It really helps to keep everything organized and easy to adjust.
Hope this helps you get it working smoothly.