Right now, if a user tries to run an import while another job is already running (via ActiveJob), the request errors out without clearly explaining why. The job may still be running in the background, but from the user’s perspective it looks like a failure. We should detect when a job is already running and prevent starting a new one. Instead of returning an error, the system should immediately respond with a clear message indicating that a job is already in progress. Ideally, the message would also include the job name (e.g., CONGRANT import) so the user knows exactly what is running.
Right now, if a user tries to run an import while another job is already running (via ActiveJob), the request errors out without clearly explaining why. The job may still be running in the background, but from the user’s perspective it looks like a failure. We should detect when a job is already running and prevent starting a new one. Instead of returning an error, the system should immediately respond with a clear message indicating that a job is already in progress. Ideally, the message would also include the job name (e.g., CONGRANT import) so the user knows exactly what is running.