CRON Trigger execution time limit for Workers Paid?

I'm on the Worker's Paid plan and I can't wrap my head around the documentation regarding CRON limits.

Do I fall under the Standard row?

FiruOP•7/5/24, 3:22 PM

So my max CPU time is 15 minutes?

FFiru I'm on the Worker's Paid plan and I can't wrap my head around the documentation ...

Chaika•7/5/24, 3:23 PM

yes you fall under standard now, but there's an exception on that same docs page

Chaika•7/5/24, 3:23 PM

On the Unbound (which should be same for Standard too afaik) billing model, scheduled Workers (Cron Triggers) have different limits on CPU time based on the schedule interval. When the schedule interval is less than 1 hour, a Scheduled Worker may run for up to 30 seconds. When the schedule interval is more than 1 hour, a scheduled Worker may run for up to 15 minutes.

CChaika > On the Unbound (which should be same for Standard too afaik) billing model, sc...

FiruOP•7/5/24, 3:34 PM

ooo okay, so basically, anything that triggers every 1hr and above can utilize the 15 minutes?

Chaika•7/5/24, 3:35 PM

should be yea, keep in mind you've still got the 128 mb limit and 1000 subrequest limit

CChaika should be yea, keep in mind you've still got the 128 mb limit and 1000 subreques...

FiruOP•7/6/24, 6:19 AM

gotcha. thanks!

FiruOP•7/6/24, 6:20 AM

by the way, do new worker instances run in different IP Addresses? Like if I rate limit my API based on the IP address, does using multiple worker instances sort of bypass this due to being "globally distributed"?

CRON Trigger execution time limit for Workers Paid?

Similar Threads

Similar Threads

Similar Threads