In-flight entry recorded too late

A cache meant to let only one caller perform a slow call decides to make the call and records 'in progress' at different moments: it writes the entry only after the result arrives, or defers the refresh decision to a later callback. Callers that arrive in between see no entry and each perform the call.

A promise cache stores the result only after the fetch returns; two components mount together, both find the cache empty, and both hit the network.

In-process dedup of one call; not a check-then-insert race on a durable job table (Parallel Admission Bypass, the same shape on disk) and not a cache that missed a refresh (Missed Snapshot Refresh).