Deduplication using Google Cloud Queue's with a Pull Model

[Austin]

I am looking at the various cloud queue options to handle webhooks that can be received multiple times and out of order, before being processed by an internal system. It seems the pull task queue is being deprecated in favor of pub/sub, but pub/sub does not offer deduplication, retries, and scheduled delivery. I only need one handler/subscriber per message and would like to pull via the api however it seems these features are exclusive to cloud tasks or pub/sub, which is made more confusing since it is possible to create cloud task pull queues. If I use a google cloud task queue how can I configure the internal system to mark it self as available to process the next message in the queue?

[Kaan]

Just use push queues with unique id's? When you get the name already exists exception, you'll know it's a duplicate, otherwise retry

I'm guessing there's a processing/cost restriction too