Possible mismatch between API scenario users and saved scenario users

[noracato]

Through the API users can alter the access for individual engine scenarios, through the ETModel interface users can manage the access for the saved scenario, and thus the full history of engine scenarios.

If one has already given other users access through the API to the last engine scenario of a saved scenario, then the saved scenario will give the error message that these users were already coupled when trying to couple them to the saved scenario in the interface.

I think this is a strange edge case, that we maybe just have to mention in the docs and leave it there. What do you think @mabijkerk?

[github-actions]

This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.