#RC#
A generic execution failure is often a protective measure built into the contract’s core logic. Several users have reported a temporary “transaction freeze” in mpl-token-metadata specifically 151. Increasing the slippage tolerance slightly can help bypass a transaction that keeps reverting. Security audits often reveal that high network demand can trigger a generic 151 exception.
Most mpl-token-metadata users find that a simple page reload fixes the “stuck button” issue 151. The final objective is to create a seamless experience where technical errors are non-existent. Sometimes a simple delay in block finality can make a successful tx look like it failed. The protocol might have a “safety lock” that was triggered by the 151 revert.
Layer 2 network delays can sometimes lead to “ghost” transactions that appear later.
