Languages & workloads
Background workers
Run persistent non-web processes such as queue consumers, automation workers, and bots without requiring public ingress.
1. Use a repository with a deterministic long-running start command
Use a repository with a deterministic long-running start command.
2. Do not make a background worker depend on receiving inbound HTTP traffic unless the application actually exposes a web service
Do not make a background worker depend on receiving inbound HTTP traffic unless the application actually exposes a web service.
3. Store credentials in project environment variables
Store credentials in project environment variables.
4. Deploy the worker and use application logs and runtime health to verify that the process remains running
Deploy the worker and use application logs and runtime health to verify that the process remains running.