Case Study: A Bug That Could Have Posted the Same Thing Twice
This series has talked about debugging someone else's infrastructure in the abstract. This part is the opposite: a real bug, in a real system, that is still running right now — the scheduler that posts this very series to LinkedIn every weekday.
The problem
The scheduler calls LinkedIn's API once a day to publish the next queued post. If that network call times out, or comes back with no clear answer, there is a real ambiguity: LinkedIn may have already published the post and only the confirmation was lost. A naive retry in that situation risks posting the exact same thing twice.
Why it happens
A failed network call only tells you that YOUR side did not receive a clear answer — it tells you nothing about whether the other side actually processed the request. Code that treats "no response" the same as "definitely failed" will retry something that may have already succeeded.
The fix
On an unclear failure, the scheduler does not guess. It parks the row as failed with its retries spent, and sends an alert asking a human to check LinkedIn directly before anything retries automatically. The system's job stops at "I do not know" — it does not pretend to know.