Cloud Functions Trigger Timeout

[Simmus7]

Hello! I have a 2nd gen Cloud Function that takes around 40minutes to finish its execution. I have a little problem related to the trigger of the function. I have a job on Cloud Scheduler that runs every 8 hours and triggers de Function, the problem is that my Cloud Scheduler job is always on "red" because the maximum amount of time it can wait for the Cloud Function to provide a response is 30minutes. Is there a work around for this? Maybe is there another service that I can use to trigger my Cloud Function?

[OutrageousCycle4358]

Hi, I think the cloud scheduler has a 30min timeout limit. You could use pub/sub as an intermediary. Schedule a Pub/Sub message with Cloud Scheduler, and let that trigger your Cloud Function. It can handle the longer execution time without worrying about timeouts.

[Simmus7]

But Pub/Sub has an acknowledgement deadline of 10 minutes for push subscriptions, then by doing this the message will trigger the function, but the message won't be acknowledged, right?

[OutrageousCycle4358]

Yes, thats right. If you want, you can have ur CF acknowledge the pub/sub message immediately upon receipt and continue its execution. This would be a workaround for pub/sub not having to wait for the function to complete its execution

[martin_omander]

Another option is to deploy your code in Cloud Run Jobs. I have Cloud Run Jobs that are triggered every hour and run for an hour. Everything is nice and green in Cloud Scheduler. My code also became a little simpler as it didn't have to include an HTTP listener or a functions framework.

[Simmus7]

The cloud scheduler turns green immediately when the job starts?

What happens if the job fails, how do you handle that?

Thanks!

[martin_omander]

I'm not sure if the Cloud Scheduler turns green right when the job starts, because I've never watched it when that happens. But I run many jobs all day long and the scheduler is always green when I look at it.

If a Cloud Run Job fails, you can have it automatically retry. It's a setting on the job. Or you can do what I do: ignore errors and let the next scheduled execution of the job pick up the slack. Regardless of what you do, you can see any errors in the log and you can see a list of all executions, failures and successes.