I have a function that takes about 10 minutes of runtime. I notice when I test this in the sandbox the function works but when I call it from the job scheduler it only runs for 6 minutes and then just stops. Is there a runtime length threshold for functions the job scheduler calls?
It’s not the job scheduler that has a max runtime. It’s the container’s max life span you’re running into (which is indeed around 6 minutes). You cannot do anything about it. Standard suggestion is dividing the Job in 2 parts, which can be difficult at times.
Sorry I do not have a more satisfying answer. BTW, is it long db-actions you are doing, or a lot of calculations?
Thanks for the response. I ended up splitting the function into 5 parts and have the end to end process working now. I am looping through a collection and updating it based off API call responses. The API request takes time and the collection has 500 items
Glad you got it working, and a good idea to split it into 5 parts: the container’s worst case lifespan is 1 minute., max around 6.
Good to know thank you