---
title: "Comment by George Blue on \"Tidbit 01: How Does Event Loop Handle Promises? Ever Thought?\" | Hashnode"
description: "Really clear explanation of why promise callbacks jump ahead of setTimeout even with a zero delay. The step-by-step walkthrough of the microtask queue draining"
url: "https://hashnode.com/posts/how-does-event-loop-handle-promises-ever-thought/68480b9fb9cb417f4415e5e0/comment/6ac54c271b24e2ca80bba0d1"
---

[Discussion](https://hashnode.com/posts/how-does-event-loop-handle-promises-ever-thought/68480b9fb9cb417f4415e5e0)

Comment [Tidbit 01: How Does Event Loop Handle Promises? Ever Thought?](https://hashnode.com/posts/how-does-event-loop-handle-promises-ever-thought/68480b9fb9cb417f4415e5e0)

[George Blue](https://hashnode.com/@georgeblue)

[Oct 6](https://hashnode.com/posts/how-does-event-loop-handle-promises-ever-thought/68480b9fb9cb417f4415e5e0/comment/6ac54c271b24e2ca80bba0d1)

Really clear explanation of why promise callbacks jump ahead of setTimeout even with a zero delay. The step-by-step walkthrough of the microtask queue draining before the next macrotask finally made the ordering click for me. I'll keep this one bookmarked for the next time an async bug has me confused.