Manuel Astudillo

In that case I think I have a better solution. I think we can add a "status" flag to the job object that is passed to the processor, so depending...

this is not possible at the moment.

if you create a new instance with a different rate limit value that one will take over.

but do not mix different queue instances with different rate limit values or is it going to give some unpredictable results...

This is not possible at the moment. Not super high priority atm since it seems quite a niche feature but this can change if many people vote for this one.

I cannot think about a workaround for this right now other than building the .ts file and use the .js file as a processor. A bit more inconvenient but with...

@Nemmo you should build your processor and use the built .js file, that is the only solution that will work for some time.

I am not really sure what you are trying to figure out. Bull does only spawn new processes if you put your process in a separate file as explained here:...

> I think the request is for something like a BULL_SANDBOX_PROCESS=1 environment variable so that arbitrary code can easily tell whether they're running in a sandbox or not. @gabegorelick but...

> a lot of time the job fails to retry because the process (in my case, 'new-job') couldn't be found, but sometimes if I try again, it works normally (the...