troubleshoot-errors

Diagnose and resolve Algorand smart contract, transaction, and SDK errors.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/Rudhrakoushik10/RootNode --skill troubleshoot-errors-rudhrakoushik10
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshoot-errors
Source: https://github.com/Rudhrakoushik10/RootNode/tree/main/projects/.opencode/skill/troubleshoot-errors
Command: npx skills add https://github.com/Rudhrakoushik10/RootNode --skill troubleshoot-errors-rudhrakoushik10

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Algorand developers frequently encounter cryptic error messages like "logic eval error: assert failed pc=123" or "overspend" without clear guidance on root causes or fixes. This Skill maps common Algorand errors to their causes and provides concrete code-level solutions. ## Core Features & Use Cases - Contract Error Diagnosis: Explains assert failures, opcode budget exceeded, ABI encoding errors, and box/state issues with fixes in Algorand Python and TypeScript. - Transaction & Account Error Resolution: Covers overspend, minimum balance requirements, asset opt-in failures, group limits, and network mismatches. - SDK Exception Handling: Addresses AlgodHTTPError status codes, confirmation timeouts, and connection failures. - Use Case: When a transaction fails with "dynamic cost budget exceeded", the Skill explains the 700 opcode budget limit and shows how to pool budget with additional app calls or split logic across multiple calls. ## Quick Start Ask the assistant to diagnose the Algorand error message you received, such as "logic eval error: assert failed pc=123", and apply the suggested fix.

Frequently Asked Questions about troubleshoot-errors

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix a logic eval error assert failed in Algorand?

A logic eval error with assert failed means an assert statement in the smart contract evaluated to false. Use the pc value in the error with source maps to locate the exact line, then check the assertion condition and input values.

How to fix opcode budget exceeded in Algorand smart contracts?

Opcode budget exceeded means the contract used more than the 700 opcode limit per app call. Add extra app calls to the group to pool budget up to 11,200 opcodes, optimize expensive operations, or split logic across multiple calls.

Why does my Algorand transaction fail with overspend?

Overspend occurs when the sender account lacks sufficient balance for the amount plus fee plus minimum balance requirement. Fund the sender account, reduce the amount, or account for the 100,000 microAlgo base MBR plus per-asset and per-app additions.

What does asset not opted in mean on Algorand?

The error means the receiving account has not opted into the asset before the transfer. Have the receiver submit an asset opt-in transaction with a zero-amount transfer to itself before sending the asset.

How do I debug Algorand transactions before sending them?

Use the simulate endpoint in AlgoKit Utils to run the transaction group without submitting it and inspect failure messages or execution traces. You can also enable debug logging via Config.configure in TypeScript or Python logging.