Laravel dispatch job execute older code version

Problem Description:

I am working with Laravel to manage asynchronous jobs for data import via a queue. In my system, each job keeps track of its state in the database in a ProgressJob model, where the states are dynamically updated during the job's flow (e.g., "Pending", "Import Finished", "Sale Opened", etc.).

Flow Details: Job State Management: Every time the job progresses (e.g., when it completes an operation like data import or sale creation), its state is updated in the ProgressJob model using the updateStatusVoucher() function. The states should be progressively updated from "Pending" to "Import Finished", "Sale Opened", "Sale Registered", etc.

Issue with the "Opening Sale" State: Although there is no direct reference to the "Opening Sale" state in my code, this state seems to "reappear" in the database after some steps, becoming the state displayed for the job, even though it is no longer used. The correct state should be something like "Import Finished", but sometimes the job reverts to the previous and obsolete state ("Opening Sale"), even though this state is no longer part of the flow.

Possible Causes: There may be an asynchronous operation (such as another worker or job modifying the state) that is causing this issue. There might be residual logic in the code that causes the job state to be updated to an obsolete or incorrect value. There could be a concurrency issue where multiple processes are trying to update the state simultaneously, causing data conflicts. Goal: Avoid the job's state from reverting to "Opening Sale" or other unwanted states, as this does not accurately reflect the job's actual flow.

Ensure that the job's state is correctly updated, maintaining consistency with the actual operations performed within the job.

Solutions Attempted: State Update Logic: I have carefully checked the state updates using the updateStatusVoucher() function, making sure the state is only changed at the appropriate stages of the job.

Concurrency Check: I have tried to prevent simultaneous updates using lockForUpdate() when accessing the job record, to avoid modifications from other processes.

Other Concurrent Processes Check: I have checked whether there are other workers affecting the job's state but have not found an obvious cause.

Question: How can I ensure that the job's state in the database does not revert to "Opening Sale" if there is no longer any reference to this state in the workflow?