Developer fixes recurring job timeouts by splitting tasks with sub-step idempotency
A developer running an automated vault-auto-ingest job faced repeated timeouts over three consecutive days when a single processing step failed to complete within its 40-minute window. The step responsible for digesting 28 hours of Claude and Codex conversation logs was too large to finish reliably during busy periods, causing a completion marker to never be set and all four daily retry slots to fail in sequence. The fix involved splitting the problematic step into two independent sub-tasks, each with its own marker file and a 25-minute timeout, so that a timeout in one would not force the other to re-run. A shared composite marker is only written once both sub-steps succeed, preserving the existing outer retry logic. This approach, termed sub-step idempotency, ensures that already-completed units of work are skipped on subsequent retry attempts within the same day.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in