Scheduled jobs
Deploy a Coderunner on a cron schedule and read type, schedule, and last run from GET/status.
workload_type=schedule plus a cron expression is a scheduled job, not an HTTP function. There is no public Deployment URL. Use Process Log / gf coderunner logs.
See also: Coderunners API · Customer Portal — Coderunner
Create and deploy
gf deploy --workload-type schedule --schedule "0 9 * * *"Or groundfloor.json workloadType: "schedule" and "schedule": "0 9 * * *". The Control Plane stores the cron on the Coderunner and sends CronExpression to Code Runner on every deploy.
What GET / status return
GET /v1/workspaces/{id}/coderunners/{id} and …/status flatten:
| Field | Meaning |
|---|---|
workload_type | schedule (not inferred as function) |
schedule | Cron expression |
last_job_name | Last Kubernetes Job / execution id (when Code Runner has reported it) |
last_job_status | succeeded / failed / running |
CLI: gf coderunner status -c <slug> prints type, schedule, and last_job.
Secrets
Do not --env KEY_SECRET=plaintext. That is 422. Store with gf secrets set KEY and deploy --secret KEY.
Tokens
Unattended Vault access: M2M (gf m2m token). Workload-identity mint returns refresh_secret on the first mint only.