Poison messages keep failing a city inspections worker. After repeated unsuccessful gets without a successful update or delete, where do those messages go on OCI Queue?
Select an answer to reveal the explanation.
Short Explanation
Each unsuccessful get without a successful update or delete bumps delivery count. Past the queue’s max attempts (1–20), the message moves to an automatic dead-letter queue so you can inspect poison work instead of blocking the main queue.
Full Explanation
Official DLQ behavior: delivery count increments on gets that are not successfully updated or deleted. When maximum delivery attempts configured on the queue (1–20) are exceeded, the message moves to the automatically created dead-letter queue (channels get their own). Operators consume the DLQ to diagnose failures; retention later expires leftovers. DLQ isolates poison messages rather than inventing a separate retry-topic product.