Open democrazyfi opened 3 months ago
Bug report
We're facing an issue where events are not de-queued in our Deno Deploy environment for the past 24 hours
We have not changed anything specific to the queue or dequeue logic
const db = await Deno.openKv(); //... const result = await db .atomic() .check({ key: keys.WEBHOOK_LOCK(txHash, webhookId), versionstamp: null }) //ensure not queued before .set(keys.WEBHOOK_LOCK(txHash, webhookId), true, { expireIn: Number(Deno.env.get("WEBHOOK_LOCK_EXPIRE_IN_MILLIS")!), }) .enqueue({ ...event, timestampMillis: Date.now() }) .commit(); console.log(`Webhook for tx ${txHash} queued`, result); if (!result.ok) { console.log(`Webhook for tx ${txHash} already queued`); }
For the same DB instance, we have the following
db.listenQueue(callback);
but the callback never gets triggered, and in the analytics dashboard we don't see any dequeue count
No response
We did previously see gep-us-east4 Error: txnproxy call timed out
gep-us-east4 Error: txnproxy call timed out
Hi @democrazyfi, in case the issue is still occurring, could you please email us at support@deno.com with your deno deploy user/organization ID so we can take a look?
š
Type of feedback
Bug report
Description
We're facing an issue where events are not de-queued in our Deno Deploy environment for the past 24 hours
We have not changed anything specific to the queue or dequeue logic
Steps to reproduce (if applicable)
Expected behavior (if applicable)
For the same DB instance, we have the following
but the callback never gets triggered, and in the analytics dashboard we don't see any dequeue count
Possible solution (if applicable)
No response
Additional context
We did previously see
gep-us-east4 Error: txnproxy call timed out