Non blocking Conductor picks up same task multiple times

[Kenshin]

When using NonBlockingConductor with redis backend, the job on jobboard gets picked multiple (n) times by same conductor and executed n times. At the end it throws error for (n - 1) since job status was modified by the first run. However, execution has already taken place. I'm using the 99-bottles example from the documentation by changing only the argument for conductor creation fro blocking to nonblocking.

[imliuda (imiuda)]

I have the same problem.