Structured error logging added to run engine triggers
The run engine now captures detailed context when background tasks fail to schedule, eliminating observability blind spots during batch processing.
When background tasks failed to trigger or schedule, the system previously swallowed some of the context needed to debug the root cause. The run engine now explicitly catches and logs detailed error states when scheduling task runs or processing batch queues.
By capturing specific failure points—like when a trigger service returns an undefined result or a queue insertion fails—these changes give developers the exact payload and environment data needed to trace execution drops. Situated in the core run engine and webapp batch handlers, this enhanced observability removes the guesswork from troubleshooting stalled or failed background jobs.