`DELETE /runs/{id}` results in HTTP 500 upon successful deletion of a run
Opened this issue · 0 comments
exodustx0 commented
This means that consumers of the API need to make two additional separate requests to verify that the run was successfully deleted — one to ascertain that the run existed to begin with, and another to verify that it is indeed deleted.