Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expertise API: don't let create a new job is there one already running with the same configuration #173

Open
melisabok opened this issue Feb 13, 2024 · 1 comment
Assignees

Comments

@melisabok
Copy link
Member

I think we should protect our API and don't let PCs to compute the scores for the same group more than once at the same time.

Sometimes they compute the setup matching without waiting for the process to complete. I suggest the API should validate if there is a job with the same request already running then throw an error and ask the user to wait until the existing job that is running to complete. Thoughts @haroldrubio @carlosmondra ?

@carlosmondra
Copy link
Member

I thought we were already doing this. Definitely, we should ask them to wait for the process to complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants