Cloud Scheduler Job pricing - need more clarity

[Brian Begun]

Hi all,

I have a question regarding pricing for Cloud Scheduler. According to this link: https://cloud.google.com/scheduler/pricing

"Each Google account gets 3 jobs per month for free."  Additional jobs cost $0.10 per job per month.

What is the definition of a job?  Is it every time a process executes?  Or is it the code that is uploaded to Google Cloud

to run an execution?

For example:  In my case, I want to schedule a Cloud Function to execute every night at midnight that will update a value in every document for a specific collection in Firestore.  Would this be considered one job?  Or will it's execution every night be the measure of a Job?

Any clarification on this would be greatly appreciated.

Thanks in advance for your help.

Best regards,

                   Brian

[yka...@google.com]

Hello,

In your case, a job is whenever Scheduler executes the function. So you would be charged $0.10 on execution of the function from Scheduler plus the charges that the function itself incurs when executing the operation.

[yka...@google.com]

I agree that the wording in the documentation is confusing so I will try to get some clarification to be sure of my answer. I will try to confirm this tomorrow.

[Brian Begun]

Thanks for checking for clarification.

Best regards, Brian

[yka...@google.com]

Hi,

I asked the product managers about this. You actually get charged $0.10 per job registered to run and not per execution so my previous message was inaccurate. However you will also be charged for the resources Scheduler invokes.

Thanks,

[Brian Begun]

That makes a lot more sense and reasonable.

Thanks for checking and clarifying.  Would it be possible to add this info to the documentation?

Thanks!

Best regards,

               Brian

[sami...@google.com]

Hi,

Thank you, I have already forwarded your request  to the Cloud Scheduler documentation team in order to add the information that the job is registered to run in Cloud Scheduler and the cost is associated with run but not function execution. Please note that for the request, we cannot offer an ETA or guarantee its implementation at this time.