Hi Brian - I just ran into this issue as well.
It would be helpful for the API to respond with a more clear message than that the `sis_id` 'is already in use' - if the sis_id is attached to a 'deleted' course - wouldn't it not be 'in use' ?

Additionally - using an API GET request with sis_id on the same deleted course returns 'The specified resource does not exist' - but this is also factually incorrect. The course does exist, but is 'deleted'. This response could also be made more clear.

With this combination, it's very difficult to determine why a course with a duplicate sis_id is failing to be created, when the API returns contrasting messages: it's in use, but also does not exist.
Thanks for any improvements here