I just created a rule, did an "Install Rule", then a "Run Actions".
This was intended to be a test for my Sonos issue--but surfaced an interesting and unexpected problem: the "Wait for Event/Elapsed Time" waits didn't wait at all (at least after the first one).
How long are the audio files? My Theory: The wait starts after each step is executed but I don't think it waits for the MP3's to complete. So, if your first MP3 is longer than the next wait, it will play the next one after the wait from the start of the prior one (not the end).
If I'm looking at your logs correctly, the waits then action seemed to follow the design. App 2543 appears to be the rule and the logs look like they are following the pattern correctly. Each wait for event - elapsed time is followed by (1) Wait Event: Elapsed Time, (2) Wait Over: Elapsed Time, and (3) Action: play track. Counting by seconds seems to indicate this. Have you filtered by just the rule?
What I am seeing in your logs is the Kitchen device (I'm assuming is a Sonos speaker) appears to be slow in logging its events. That is why the device TrackDescription is later than the Action from the Rule. Did the mp3s play correctly? What did you actually hear when running the rule?