What will happen if a cron is triggered, and it's a long running process, and then another cron is t
What will happen if a cron is triggered, and it's a long running process, and then another cron is triggered?
On the Unbound 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.
remote flag, and in my console output I'm getting lots of [object Object] references for things that are definitely not, 100% note, objects - they're just strings. This is shown by instead logging the result of encodeURIComponent(myStr), and the problem goes away. Obviously it's hard to give a reproducible example, but is there anything that might be causing this? It's just started happening today, in multiple endpoints of my code, and wasn't happening before.[object Object]. This would obviously result in a query failure, but the query runs fine, which again suggests that this is some sort of illusion in Workers or the Workers console output.