A few thoughts about different ways to go at it:
A checkbox on the ticket creation process that says to pause for 1 second, or even half a second, afterwards. If that isn’t enough, this is a bad idea. The current time between the start of each task is 17 milliseconds in the failed examples, so a half-second would be multiplying that by ~30.
I wonder if the fields of a new ticket are always written in the same order. Could Email2AT always put a certain value in a certain field that comes at the end of the process and check that it has the correct value as an approximate sign that the ticket is done being created?
A thought for doing this with Email2AT without enhancements; going back to my earlier suggestion. In the step that changed the contact to 594, if we check for the contact being set as 776 in a loop that tries up to x (5 - 15) times, we would know that the prior step got past that field. We do not have any other workflows that change the contact, so in this particular case, we might be ok.