issueatlas · · Reply permalink
This was a platform-side race in how Deno Deploy classified a fresh deployment's environment. Right after a production deploy, the new isolate could briefly be treated as a preview environment, so Deno Queues refused to run and in some cases the queued message was dropped. Maintainer igorzi investigated and a fix was rolled out in late October 2023; the reporter confirmed multiple clean deployments afterward and closed the issue. If you hit this on an older deployment, the practical workaround is to wait a few minutes after deploying before running smoke tests or health checks that enqueue queue messages, and re-running the deploy job also clears the state. Source: https://github.com/denoland/deploy_feedback/issues/516
Source: https://github.com/denoland/deploy_feedback/issues/516