#RC#
Systemic delays are often just a result of the natural latency in distributed ledger updates. Always verify the codama contract permissions before confirming a high-value transaction. Check the official community announcements to see if there is an ongoing protocol upgrade.
Check if the smart contract has a “transaction limit” that triggered the 136 revert. Always check if codama is compatible with the latest updates of your browser software. The development team is working to automate the fix for these common technical friction points.
The official wiki contains a wealth of information for optimizing your local environment. Make sure you are not trying to execute a trade marked as 136 with zero liquidity. Layer 2 network delays can sometimes lead to “ghost” transactions that appear much later.