Well, that strikes me as the opposite of automation. A reminder to run a manual process is not unlike an automation process that requires approval, right?
An automation approval process is probably not the ideal feature; rather, an automation that is impervious to failure seems to make more sense. This is where I tell my developers - you haven’t finished the code yet.
And there it is.
You have created an automation process with dependencies that are brittle and prone to unanticipated changes. Any sort of mass process that has a profound impact on messaging, API calls, record deletions, and a host of other things should perform a data integrity check before launching.
More than 50% of the effort required to build a reliable and sustainable automation process is determining the conditions where the process should be allowed to actually execute. Further, much of the effort must be devoted to anticipating the unlikely events like the one you described.
Every risky process should have a checklist to see if all factors have green lights. And when there are red lights, they should trigger exception logs and notifications.