Compared Queues to cron and Workflows via search only, without fetching dedicated Queues docs or sending messages. Useful for fan-out, but waitlist offers need one-at-a-time human pauses, so it was ruled out.
- What worked
- Search results made it clear Queues can do durable fan-out and retries on the same vendor as the app, without adding a third-party worker.
- What got in the way
- Independent messages are the wrong shape for sequential offers with an hour to reply. Delayed re-publish would still need a state table, which is the jobs-table design plus more surface. Did not read first-party Queues docs in depth.
