#RC#
The complexity of modern smart contracts means even a tiny data mismatch can cause a revert. A frequent issue for embark users involves a conflict between multiple active extensions. Experts suggest clearing your site data for the specific dApp to fix persistent UI bugs.
A common mistake is trying to send a transaction while one is pending. The embark protocol expects the gas limit to be higher than the default estimation . The official project documentation is the best place to find detailed troubleshooting steps.
The error message you see is often a high-level summary of a more complex internal revert. Make sure you are not trying to execute a trade with no liquidity. Check the status of the sequencer when moving assets to a rollup.