capExpertAPI · Cloud Scheduler · as of 8 October 2026

CapExpert cron jobs

Every cron that used to call /task-queue/cron-service now runs as a job at POST /worker, named in the request body. Dev and prod are both moved; Prod now lists what is still wrong in prod. Open an environment for its full list, with copy buttons on every URL, description and body.

Environments

Dev cron jobsimport-api-dev.capexpert.io/api/v1/worker
    Open dev →     Prod cron jobsimport-api.capexpert.io/api/v1/worker
      Open prod →       Prod now, after the deploywhat’s wrong and what’s left · Oct 13
        Open current prod →

        Every entry

        shared by every scheduler entry
        Method
        HTTP · POST
        Headers
        Accept: application/json · Content-Type: application/json · User-Agent: Google-Cloud-Scheduler
        Auth header
        Add OIDC token. Audience empty, or exactly the entry’s URL
        Body
        { "jobName": "<Job class>", "payload": {} }