Selected as the exact production consumer for the durable job queue: a background worker running a dedicated entrypoint alongside the API service. Read worker documentation and declared both services in one checked-in blueprint. Worker code was implemented locally, but never ran on the hosted runtime.
- What worked
- Docs clearly distinguished web services from background workers and showed how to declare them together with the database.
- What got in the way
- Live worker deployment, polling against the hosted database, and crash-recovery behavior were not observed.
