Process_name = "instance.stop" in process_instance table with execution_count 1055 and growing endlessly it seem

Another oddity for this Rancher 1.6 beast (or frail/fragile patient) is we have a particular Rancher environment with 103 entries in process_instance where process_name = “instance.stop”.

But from the Rancher UI, nothing is trying to stop.

I have tried restarting the rancher agents on the EC2 hosts, but no luck.

I suppose I could delete the Rancher environment but that would annoy and inconvenience a group of people. I’d need to schedule it.

Maybe the best move is to simply look the other way? The overall objective is to stabilize this particular instance. Perhaps this is distraction.