Juan Cruz-Benito

We need to replicate the error to understand what is happening and later fix it. That is the info. But thanks for your reply, @ccpalmer

Hi @MatthewGregoire42! Thanks for your issue. We'll solve it as soon as possible. Kind regards

Hi @AkashGutha For now, we don't have access to a public API that provides this kind of info. We are talking with other colleagues at IBM to expose this info....

Yes, it seems to be a problem related to having white spaces in the path. We don't have much more info. For now, we should add a python method to...

Hi @pacomf and I are trying to implement this `processOnce()` method. We have a preliminary proposal [here](https://github.com/cbjuan/bull/blob/add-processOnce/lib/queue.js#L648) supported by [some changes in Bull](https://github.com/cbjuan/bull/commit/ea2aaf9c3f450a10d3d65aba6ec1d1e3adf02385). We would like to discuss the implementation...

In our case, we added the third param (`notFetch`) to `job.moveToCompleted()` to automatically retrieve the next job in the queue -> https://github.com/cbjuan/bull/commit/ea2aaf9c3f450a10d3d65aba6ec1d1e3adf02385

We have detected some performance issues when using our `processOnce` method. These issues related to drained queues and `getNextJob()`&`brpoplpush()` methods. To solve that, we have modified `getNextJob()` to use `rpoplpush()`...

All the last suggestions you proposed have been addressed. The current changes in this context are listed in https://github.com/OptimalBits/bull/compare/master...cbjuan:add-processOnce

@doprdele Our POC was submitted for review https://github.com/OptimalBits/bull/pull/1066. It was closed because the library now implements most of the code to use this kind of processing.

hey @doprdele I don't know every detail of how it can be implemented right now; when we closed the PR it could be done like this https://github.com/OptimalBits/bull/pull/1066/files#diff-b68fbb0f945cdf9cddec65ddf0fbe456R648-R673