Scheduled jobs

Scheduled jobs run an application task once at each scheduled time. Use them for maintenance, imports, publishing and similar application work.

Create a job

Choose the execution type, task target and schedule. Jobs can be enabled, disabled, run immediately, inspected through Logs and deleted.

• PHP / Node.js / Python jobs run a Site-relative application target.
• Docker / Compose jobs run against the selected managed container/service.
• HTTP Request jobs perform a protected GET request and require a successful HTTP response according to the configured response policy.

HTTP Request jobs

A successful HTTP status proves the request/response policy passed; it does not generically prove every application-side effect. When the endpoint has an application-specific success contract, make the endpoint return a failure status when that contract is not satisfied.

A Control-owned HTTP job targeting its own Site uses the trusted local Site route when possible, so the Site WAF does not need to be disabled just for that scheduled request.

Python runtime dependencies

A Python job can depend on a Site virtual environment. If an imported environment is not usable on the destination, Control treats the Python runtime as a repairable dependency. The job waits while that runtime is repaired or rebuilt instead of repeatedly running with the wrong interpreter.

Results and side effects

Last Result reports the execution outcome Control can verify, such as process exit status or HTTP status. Job side effects belong to the application and are not automatically rolled back just because a job fails.