The key output order is Promise { 'saved' }. Calling an async function gives you the promise unless you await it.
The UI, test, redirect, or log moves forward before the async result is actually ready. Missing awaits can cause loading states, redirects, or assertions to run too early.
Forgetting `await` in tests, handlers, and data loaders.
Await real dependencies, start independent work together, and choose the loop pattern that matches the behavior you need.
const [user, posts] = await Promise.all([ fetchUser(), fetchPosts() ]);
The console lane proves the visible order: Promise { 'saved' }. The active line and queues show why source order changed.
Measure before and after with logs or test spies: the dependent line should run only after the awaited operation finishes.
Related cases
Continue with nearby confusion while the mental model is fresh.
Was this clear?
This stays local for now. It helps you track where the product still needs sharper cases.