Price Cloud Scheduler jobs plus the downstream invocations they trigger, and check for overlapping cron runs.
Cloud Scheduler itself is priced per job per month rather than per execution, so frequency costs nothing at the scheduler — the per-run cost lands on whatever it triggers. The interesting engineering constraint is timing: if a target takes longer than the interval between triggers, Cloud Scheduler will start another run anyway. A minute-by-minute job whose target takes ninety seconds will quietly build a queue of overlapping executions, which corrupts data far more often than it costs money. Confirm the per-job price in the Google Cloud pricing calculator and check the target service's own per-invocation charge, which usually dominates this bill.
Cloud Scheduler Cost
cost = (jobs − free jobs) × job price + jobs × runs per day × 30.44 × (1 + retry share) × downstream invocation cost; interval = 86,400 ÷ runs per day.
cost = (jobs − free jobs) × job price + jobs × runs per day × 30.44 × (1 + retry share) × downstream invocation cost; interval = 86,400 ÷ runs per day. Cloud Scheduler itself is priced per job per month rather than per execution, so frequency costs nothing at the scheduler — the per-run cost lands on whatever it triggers. The interesting engineering constraint is timing: if a target takes longer than the interval between triggers, Cloud Scheduler will start another run anyway.
A minute-by-minute job whose target takes ninety seconds will quietly build a queue of overlapping executions, which corrupts data far more often than it costs money. Confirm the per-job price in the Google Cloud pricing calculator and check the target service's own per-invocation charge, which usually dominates this bill.
This calculator takes 8 inputs: Scheduler jobs, Price per job, Free jobs per billing account, Runs per day per job, Runs that need a retry, Cost of one downstream invocation, Average target run time, Attempt deadline. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.
Cloud Scheduler will not skip a trigger because the previous run is still going. Make the target idempotent, hold a lease or lock for the duration of the work, or have the job exit immediately if a run is already in progress.