When the rebalancer is finished, its sending a messages to be executed by the valence account (send funds to auctions)
There are several reason this message can fail:
The user is not a valence account, and doesn't implement the message we try to execute
The user is not a contract, we can't execute a message on it (a wallet)
Sending the funds to an auction failed because of an error
A bug on our part in constructing the message
Random bug we missed
Doing #4 will avoid reaching the 1 and 2 errors, so they should never happen.
Because our errors are failing gracefully, and doesn't fail the whole TX, we will never actually know of errors unless we track them some way (either in storage, or an indexer that tells us if an error event happened)
Of course 3 and 4 are detectable during tests, and we should discover them early, but mistakes happen and we still want a way to see errors in production.
When the rebalancer is finished, its sending a messages to be executed by the valence account (send funds to auctions)
There are several reason this message can fail:
Doing #4 will avoid reaching the 1 and 2 errors, so they should never happen.
Because our errors are failing gracefully, and doesn't fail the whole TX, we will never actually know of errors unless we track them some way (either in storage, or an indexer that tells us if an error event happened)
Of course 3 and 4 are detectable during tests, and we should discover them early, but mistakes happen and we still want a way to see errors in production.
Thoughts?