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.
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.