I don't know if I understood your question correctly, but you can configure your queue so it launches several workers at the same time (every worker in a single trait, with no shared data).
Trying to answer to your question yes, it will fire a job (in another worker) even though the previous process hasn't started.
Sign in to participate in this thread!
