Skip to content

fix(shared): identify queue re-defer failures in logs - #1536

Open
Naveen Chatlapalli (1aifanatic) wants to merge 1 commit into
microsoft:mainfrom
1aifanatic:fix/1056-queue-defer-observability
Open

Naveen Chatlapalli (1aifanatic) wants to merge 1 commit into
microsoft:mainfrom
1aifanatic:fix/1056-queue-defer-observability

Conversation

@1aifanatic

Copy link
Copy Markdown

Fixes #1056.

When queue visibility re-defer fails, the worker still leaves the run untouched and lets the message resurface. The existing warning now includes structured event: "defer_failed", messageId, and queueName fields so operators can count and investigate repeated failures.

The queue scheduling documentation describes the event. The focused test confirms the failure is logged with those fields and remains swallowed.

Validation: pnpm exec vitest run packages/shared/src/queue/base-queue-processor.test.ts (14 passed); pnpm --filter shared exec tsc --noEmit; git diff --check.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add observability for safeDeferMessage failures in queue redelivery path

1 participant