How do you dispatch generation jobs to a worker safely?

How do you dispatch generation jobs to a worker safely?

Dispatch connects the application’s job record to execution. A reliable design handles both duplicate delivery and failures between recording and sending work.

Keep messages small and trustworthy

Send a stable job or attempt identifier and let the worker load authorized input from trusted storage. Avoid embedding large media or long-lived credentials in messages. Authenticate the dispatch path so arbitrary callers cannot trigger private or expensive processing.

Handle partial dispatch

Record whether work is pending dispatch and reconcile jobs that were saved but never sent. If a send succeeds but its response is lost, repeated dispatch must not corrupt the intended result. A managed queue such as Cloud Tasks can deliver work more than once, so handlers need safe repeat behavior. Test both sides of the send boundary and confirm the portal does not report completion merely because dispatch succeeded.

Further reading: Cloud Tasks execution model.