> For the complete documentation index, see [llms.txt](https://help.defisaver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.defisaver.com/general/troubleshooting/im-getting-an-issue-was-detected-with-this-transaction-that-would-cause-it-to-fail-error.md).
# I'm getting "An issue was detected with this transaction that would cause it to fail" error
A warning about detected issues with your attempted transaction can sometimes be seen at the transaction confirmation screen, similar to the example screenshot below.
This error means that there's something wrong with the logic of the transaction that would cause it to revert, and an additional indicator of such issues is the extraordinarily high transaction cost, as also visible in the screenshot above.
{% hint style="danger" %}
*Whenever you see this error **we DO NOT recommend proceeding** as it will almost certainly result in a failed transaction and needlessly wasted ETH on transaction fees, since gas is still paid for transaction execution, even if it ultimately reverts.*
{% endhint %}
There are a few things that you can try to resolve this:
* Try refreshing your page and making the same action again
* Try disabling any script-blocking extensions that you have enabled in your browser
* Try using a different browser
* Try using a different amount
If none of the above helps, please feel free to reach out to our team, either using the in-app help chat widget or through [our discord server](https://discord.gg/XGDJHhZ).
In cases where slippage settings might be preventing the transaction from succeeding, our interface will offer users an alternate swap route:
{% hint style="warning" %}
*Please note that this feature is not available on Maker and CurveUSD, so on these protocols, you'll still see the "An issue was detected..." warning even if slippage is the reason why.*
{% endhint %}