User Story
As a system operator, I want scheduler errors from the ETL skip guard to be caught and logged rather than crashing the cron handler, so that transient database issues don't silently kill scheduled sync jobs.
Definition of Done
Acceptance Criteria
- Given a DB connection error occurs inside
getLastSuccessfulStepRun(), the cron handler catches it, logs it, and returns without crashing
- Given the guard succeeds normally, step execution continues as before
Technical Elaboration
Currently in CatalogEtlScheduler, shouldSkip() is awaited before the try/catch, so any getLastSuccessfulStepRun() DB error escapes the cron handler unhandled. Moving the await inside the try/catch (or wrapping the entire method body) is sufficient to fix this.
Identified in PR #220 review (thread PRRT_kwDOMAoKhM6E5X2n).
Design Elaboration
No UI changes required.
User Story
As a system operator, I want scheduler errors from the ETL skip guard to be caught and logged rather than crashing the cron handler, so that transient database issues don't silently kill scheduled sync jobs.
Definition of Done
shouldSkip()(orgetLastSuccessfulStepRun()) call is inside the try/catch block in each scheduled method inCatalogEtlSchedulerAcceptance Criteria
getLastSuccessfulStepRun(), the cron handler catches it, logs it, and returns without crashingTechnical Elaboration
Currently in
CatalogEtlScheduler,shouldSkip()is awaited before the try/catch, so anygetLastSuccessfulStepRun()DB error escapes the cron handler unhandled. Moving the await inside the try/catch (or wrapping the entire method body) is sufficient to fix this.Identified in PR #220 review (thread PRRT_kwDOMAoKhM6E5X2n).
Design Elaboration
No UI changes required.