fix: backwards compatible snapshot runStatus to prevent DEQUEUED status from breaking older runners (#2335)
🚀 Publish Trigger.dev Docker / units (push) Failing after 0s
🚀 Publish Trigger.dev Docker / typecheck (push) Failing after 3s
🚀 Publish Trigger.dev Docker / publish-webapp (push) Has been skipped
🚀 Publish Trigger.dev Docker / publish-worker (push) Has been skipped
🚀 Publish Trigger.dev Docker / publish-worker-v4 (push) Has been skipped
🚀 Publish Trigger.dev Docker / units (push) Failing after 0s
🚀 Publish Trigger.dev Docker / typecheck (push) Failing after 3s
🚀 Publish Trigger.dev Docker / publish-webapp (push) Has been skipped
🚀 Publish Trigger.dev Docker / publish-worker (push) Has been skipped
🚀 Publish Trigger.dev Docker / publish-worker-v4 (push) Has been skipped
This commit is contained in:
@@ -277,7 +277,8 @@ export class ExecutionSnapshotSystem {
|
||||
description: snapshot.description,
|
||||
previousSnapshotId,
|
||||
runId: run.id,
|
||||
runStatus: run.status,
|
||||
// We can't set the runStatus to DEQUEUED because it will break older runners
|
||||
runStatus: run.status === "DEQUEUED" ? "PENDING" : run.status,
|
||||
attemptNumber: run.attemptNumber ?? undefined,
|
||||
batchId,
|
||||
environmentId,
|
||||
|
||||
Reference in New Issue
Block a user