Possible negatives with cancelling all failed commands?

[baldric-caroten]

Background:

Some of our computer configuration profiles were failing due to changes in our environment. We've set the scope of these profiles to blank (selected computer, selected user, with nothing selected for either) so they would no longer be pushed to any computer, but so they stay in our Jamf instance for educational/historical/logging reasons (as opposed to just deleting them). 

This was around two months ago, but we can still see "failed commands" from as recent as yesterday under some computer. Secondary question, why is this?

Main Question:

If we were to cancel all failed commands (search for all computers, mass action, cancel failed commands), that would cancel failed commands for profiles that should be installed as well, and would otherwise retry and (hopefully) succeed in the future. For these cancelled but still scoped profiles, will jamf try again on coming check-ins?

Appreciate any guidance

[Ecco_Luke]

Shouldn't be any issue at all with cancelling failed commands as, by virtue of them having failed, they've done nothing. Given that the profiles aren't scoped anywhere, Jamf Pro shouldn't attempt to re-push them.

If in doubt, test on one Mac and see 😊 

[DBrowning]

We currently have an open ticket with Support around Config Profiles that have been deleted still trying to push to machines and failing so we see a massive list of failed commands on some devices.  Apparently there maybe some PI about this but they (support) are still digging.  So I can clear the failed commands, but it will just start coming back.