Automated repair/restart attempt of offline Automate agent via Control agent

We've seen numerous times where the Automate agent goes offline but the Control agent is still connected and online. This causes machines to be purged from the Automate server when they are not truly offline for X days (to free up licenses.) If there were a way to have the two heartbeats check one another and if Control could attempt a restart of the Automate agent and vice versa if out of sync for X mins, that could eliminate false offline agents. And if the service fails to start or not found, generate a ticket.