Scheduling & Tasks

The cron and queue surface — see what’s scheduled, and control a Cloud Scheduler job the moment it misbehaves. Reads run under your identity; every Scheduler change is approval-gated.

Cloud Scheduler

• list_scheduler_jobs(location, project_id) — the jobs in a location, each with its state and cron schedule. Scheduler is regional, so pass the location (e.g. us-central1).
• pause_scheduler_job(job, location, project_id) — write. Stops a job from firing until resumed — the one move you want when a job is misbehaving at 3am.
• resume_scheduler_job(job, location, project_id) — write. Re-enables a paused job.
• run_scheduler_job(job, location, project_id) — write. Forces one immediate run, independent of the schedule — handy to re-drive a job that just failed.

Cloud Tasks

• list_task_queues(location, project_id) — the task queues in a location and each one’s state (running, paused, disabled). Regional, so pass the location.

Cloud Tasks is read-only today — enoki shows you queue state, but draining or purging a queue stays in your own tooling.

The identity & approval boundary

Every Scheduler write names the exact job, location, and action; if anything about it changed between the proposal and your click, the approval is void and nothing runs. See Guardrails.

Next: Build & Artifacts.