An action that has been Stopped or Expired at the server cannot be reopened or reactivated.
I can only think of a couple of situations where the client could run the action again…
-
The client has not gathered updates from the Server since the action was stopped, so the client doesn’t know the action was ever stopped. Check the BESClient log on the endpoint for gather errors.
-
The client was restored from a backup or rolled back on a VM Snapshot from before the client gathered the stopped action, and ran the action again before gathering the site update that stopped the action.
If you want to investigate further I think you’d need to open a support ticket and upload your client logs and screenshots of the action configuration (showing the action ID, time issued, time stopped, etc.)