When enqueuing clear concurrency for that run

[matt-aitken]

It was possible in some edge cases for the concurrency to be taken by a run and the message to get enqueued again without the original concurrency being cleared. This causes problems if you're maxed out with your concurrency (at the org, environment, or task/queue level).

The change here remove the concurrency keys when enqueuing, since obviously it's not running if we're enqueuing.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 2ee3b7c

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

commit: 2ee3b7c

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/build@1271

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev@1271

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/core@1271

pnpm add https://pkg.pr.new/triggerdotdev/trigger.dev/@trigger.dev/sdk@1271

Open in Stackblitz