A user creates a new scene with name 'abc', but that user already has a scene with the name 'abc'. As a result, the newScene function will fail.
Status Quo:
The user is bounced to the scene-list/previous page. No explicit feedback is given to the user that the chosen scene-name is unavailable since they have already used it.
Ideally:
The user is given a message in-context of the create new-scene dialog telling them that the name is taken and encouraging them to choose a different name.
Complication:
On the server side, care has to be taken to separate failures due to name conflicts with other sorts of errors that could occur. Other errors should probably be handled differently.
Scenario:
Status Quo:
Ideally:
Complication: