Scenario locking

Anyone else experiencing a problem with shared scenarios, in which when one person opens the scenario and then exits, CVR insists that they still have it open and don't let another developer open it?

Discussion (2)

Make sure that when you are exiting the edit session on the shared scenario, that you exit back to the dashboard before closing the window to clean things up. It does prompt you with a warning if you just close the window in the middle of an edit session.

Exit, then sign out? OK, is that documented anywhere? The generic "leaving the page" warning doesn't really make it clear. Thanks.

Make sure that when you are exiting the edit session on the shared scenario, that you exit back to the dashboard before closing the window to clean things up. It does prompt you with a warning if you just close the window in the middle of an edit session.