A GIS export worker pulled a Queue message but processing will exceed the remaining visibility window. What should the consumer do so the message does not return mid-work?
Select an answer to reveal the explanation.
Short Explanation
If work will beat the hide window, update the message to extend invisibility. That is the “update” principle. Bumping the queue-wide default is blunt; per-message update is precise. Functions timeouts are a different clock.
Full Explanation
Official consume guidance: when processing will exceed remaining visibility, the consumer updates the message to extend invisibility so it does not reappear mid-work. Raising the queue default visibility is coarser. Deleting early risks loss if the worker fails afterward. Function execution timeouts are unrelated to Queue visibility and do not replace the update call.