The transaction retry mechanism has problems with the way that it is setup. It should be removed in favour of having the user retry the transaction from where it was first initiated.
For example, if a transaction fails / is rejected as part of an action saga, it should be possible to retry the entire saga from the action form. If a transaction fails / is rejected when installing an extension, it should be possible to retry installing the extension. If a transaction fails / is rejected when creating a colony, it should be possible to retry creating the colony, etc. Rather than retrying just the individual transaction as the transaction retry mechanism currently does.
One example: Steps to reproduce
Create a "Create new team" action via the action sidebar
Reject the transaction
Expected behaviour
An error / warning validation message shows and the entire action can be retried by re-submitting the form
Actual behaviour
The UserHub transactions list opens and allows you to reattempt the individual transaction which will fail to create the associated metadata in the database causing issues with missing team names and other missing metadata.
Description
The transaction retry mechanism has problems with the way that it is setup. It should be removed in favour of having the user retry the transaction from where it was first initiated.
For example, if a transaction fails / is rejected as part of an action saga, it should be possible to retry the entire saga from the action form. If a transaction fails / is rejected when installing an extension, it should be possible to retry installing the extension. If a transaction fails / is rejected when creating a colony, it should be possible to retry creating the colony, etc. Rather than retrying just the individual transaction as the transaction retry mechanism currently does.
One example: Steps to reproduce
Expected behaviour
Actual behaviour