X_JOB_CRASH_DIVERGED
Means
a job run killed at a step boundary made an effect a different number of times than a clean run
Typical cause
an effect — a row write, a mail, a call out, an enqueue — sits outside every step.run, so the retry after a crash makes it again
Fix
step.run('<name>', async () => …) around the printed effect, in the job crashProof named; then: x test job --filter <the test file>