Silent workflow bug reported 'success' 27 times daily while skipping all real work
A developer discovered that 27 workflow branches were being silently skipped every day, yet each run was marked as COMPLETED with no warnings. The root cause was an enum value, StepExecutionStatus.SKIPPED, that had existed in the codebase since the project's start but had never actually been written to the database. Skipped steps left no database rows, making them invisible in the UI and impossible to query without manually parsing a JSON blob. The fix involved writing real database rows for skipped steps and adding run-level counts for processed, skipped, and failed steps. The incident highlighted a broader problem: health checks and status indicators can appear green while the system silently does nothing meaningful.
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