Running a computational service twice results in three requests to the backend because the second always fails with a 422
Expected behaviour
I would expect a single POST *:start request per run-hit
Actual behaviour
on second run, the front-end always retry because it consistently fails with 422 (in all environments) and
{"data": null, "error": {"errors": ["Project (uuid) has no computational services, or contains cycles"]}}
Steps to reproduce
open dev pannel.
open a study.
add a sleeper and hit run. -> produces first POST
When fininished, hit run again -> produces a POST that fails and a second retry that will go thru
Note: your environment was attached but will not be displayed
Long story short
Running a computational service twice results in three requests to the backend because the second always fails with a 422
Expected behaviour
I would expect a single
POST *:startrequest per run-hitActual behaviour
on second run, the front-end always retry because it consistently fails with 422 (in all environments) and
Steps to reproduce
open dev pannel. open a study. add a sleeper and hit run. -> produces first POST When fininished, hit run again -> produces a POST that fails and a second retry that will go thru
Note: your environment was attached but will not be displayed