Hi @merefield Thank you for the replay
What do you mean by exactly by “concurrency” issue? Can you please elaborate? What is happening out of order exactly?
As I mentioned above, on preprod and production environment more than one sidekiq process running.
I’m not sure! The job might confuse when it tiger which process it should take because of the multi worker process.
Also “skipping code execution”. Can you elaborate? What code? When a job runs the code will not be skipped. Have you checked your /logs that nothing is breaking?
We’re running some custom sidekiq jobs which are export some custom sats on CSV file. The job is running periodically. Sometimes the file export does not happening. The job runs without any error message.
For ex:
For the testing purpose, If I click this trigger button the job is running but the file export does not happening sometimes.
FYI, on Dev env same code running but it’s only one sidekiq worker process.Here working fine. I’m wondering the issue is because of more than one sidekiq process running on the prod/preprod.
Have you checked your /logs that nothing is breaking?
Yes, We didn’t get any error related to the job
And be aware you might be running an unsupported install
We’re running latest discourse version.
Thank you