Transaction retries after Indexer unregister

[jim-counter]

Maybe just an observation but I notice that the coordinator appears to be retrying a transaction after unregistering. Shouldn't it be idle?

coordinator_service  | 2022-05-21T11:55:18.237Z <network> INFO currentEra: 573 | lastClaimedEra: 571 | lastSettledEra: 571
coordinator_service  | 2022-05-21T11:55:18.239Z <transaction> INFO collect and distribute rewards: PROCESSING
coordinator_service  | 2022-05-21T11:55:52.277Z <transaction> INFO collect and distribute rewards: SUCCEED
coordinator_service  | 2022-05-21T12:05:18.089Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:20:15.258Z <contract> WARN insufficient balance for the controller account
coordinator_service  | 2022-05-21T12:25:12.342Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:25:13.866Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:25:15.589Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:25:17.761Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:25:22.286Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:25:23.945Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:30:11.695Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:30:13.240Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:30:14.791Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:30:16.359Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:30:17.881Z <network> INFO retry to send transactions
coordinator_service  | 2022-05-21T12:30:19.413Z <network> INFO retry to send transactions