A job is a resource that stores work configuration separately from execution. Create and configure it once, then invoke its parameterless run method whenever the work should occur. section 11.2
Use the split between configuration and execution to:
- Avoid repeating increasingly large configuration payloads. section 11.2
- Grant configuration and execution permissions independently. section 11.2
- Support scheduling by invoking one parameterless method. section 11.2
- Keep execution inputs on the job; run should accept only the job identifier. section 11.3.2
Rerunnable backup job
Create and configure a backupChatRoomJob, then call POST /backupChatRoomJobs/{id}:run. The call returns a long-running operation whose response can contain a destination and whose metadata can report messages counted, messages processed, and bytes written. section 11.3.2
Follow the interaction sequence from job creation and configuration to later execution. section 11.2



