You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the code for the Azure Storage Queue service is written in such a way that if a mapgl-tile-renderer worker receives a message that it cannot process due to invalid input options, it maintains a claim on the message but does not perform any further actions (such as deleting the message). This is causing deployment issues where phantom messages remain in the queue, unprocessed by the workers. Let's improve this by deleting the message from the queue and logging the event.
The text was updated successfully, but these errors were encountered:
Currently, the code for the Azure Storage Queue service is written in such a way that if a mapgl-tile-renderer worker receives a message that it cannot process due to invalid input options, it maintains a claim on the message but does not perform any further actions (such as deleting the message). This is causing deployment issues where phantom messages remain in the queue, unprocessed by the workers. Let's improve this by deleting the message from the queue and logging the event.
The text was updated successfully, but these errors were encountered: