Get All Latest that never completed

[ken.norcross]

We had a user of a shared model (DB + VCS) mistakenly execute a Get All Latest command. The user eventually closed Sparx, but now, weeks later all users of the shared model still get a warning that the Get All Latest command has not finished.

Is there any way to cancel this?

[Boron]

I don't know if the unfinished "Get all latest" can be cancelled "globally" for the model.

What I do know: A user trying to checkout a package and getting  the message "Get all latest in progress. Continue anyway?" (or something like that) can simply continue.
The checkout will be performed without problems.
This is not a real solution, but it ensures that working can be continued.

[qwerty]

Don't use VC on a central repository but only with distributed EAP files. Use EA security when working on a central repository and take nightly snapshots. That's not only faster but also prohibits wrong use of get all latest.

q.

[Boron]

... but also prohibits wrong use of get all latest.

Use EA security and create a "Developer" user group that does not have the right to invoke "Get all latest...".
All users except "key users" (e.g. dedicated admins or SW architects) should be part of that group.