Hey guys, for long running tasks, like processing a large database dump or using some browser automation, is locking a worker on it the only way to do so? Given the limited amount of workers we can spin.
TL;DR
Question: Is locking a worker the only way to handle long running tasks, considering the limited number of available workers?
Solution: One possible solution to handle long running tasks without locking a worker is to use task queuing and scheduling systems like Celery. This allows you to distribute the tasks across multiple workers and prioritize them based on their importance and resource requirements. This way, you can handle long running tasks efficiently without blocking available workers.Recommended threads
- Error trying to deploy functions from CL...
✗ Error • on-auth-create (6a00b2ab000c9ce2949b) • Server Error ✗ Error: No functions were pushed. Prject ID: 69ffe0270033a4ac420a
- Intermittent Deploy and Execution Errors...
Project: project-fra-658e2f5f4ba30df91177 Function ID: 69bde006001c56757f49 **Several execution errors with:** Timed out waiting for runtime.\nError Code: 400...
- ~20 function variables disappeared
Hi, In one of my functions about 20 variables just disappeared. The "Next" button also seems to be bugged. The "total variables" text still says the correct amo...