josh 8f35724bde fix: queue on-create jobs sequentially and fix history ordering ...

runJobsOnCreate now awaits each job before starting the next,
ensuring they don't stomp each other's DB writes in parallel.

getInstanceHistory changed to ORDER BY changed_at ASC, id ASC so
the creation event (lowest id) is always first regardless of
same-second timestamps.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-03-28 20:09:32 -04:00

15 KiB

Raw Blame History

View Raw