
Iii Error Handling
Teaches Claude how to handle errors in the iii platform by branching on specific error codes like `function_not_found`, `FORBIDDEN`, and `timeout` instead of parsing message strings. Covers the distinction between SDK-local errors and engine-side invocation failures, plus retryability rules (don't retry RBAC denials, be careful with timeouts unless your work is idempotent). Includes working exception handling patterns for Node, Python, Rust, and browser SDKs. The honest take: error codes in distributed systems always feel like they need one more layer of context, but having a reference that tells you not to retry `FORBIDDEN` blindly is worth it when you're debugging at 2am.
- skills.sh installs
- 4.7K
- GitHub stars
- 18.9K
- last updated
- Aug 21, 2026
Install
$ npx -y skills add iii-hq/iii --skill iii-error-handling --agent claude-codeInstalls into .claude/skills of the current project.
Files
Error Handling
iii has two broad error classes: SDK/local errors and engine/remote invocation errors. Agents should branch on the error code instead of matching only message strings.
Error Codes
Branch on exact code strings, but keep engine wire codes separate from SDK-local codes.
Sponsors
Details
- Repository
- github.com/iii-hq/iii
- Categories
- Security, Debugging, Automation & Workflows, Python, Rust
- First seen
- Jul 14, 2026
More from iii-hq/iii
All 30- Iii Architecture Patterns4.7K
- Iii Core Primitives4.7K
- Iii Sdk Reference4.7K
- Iii Observability195
- Iii Browser Sdk194
- Iii Trigger Actions194
- Iii Workflow Orchestration194
- Iii Agentic Backend193
- Iii Channels193
- Iii Custom Triggers193
- Iii Event Driven Cqrs193
- Iii Functions And Triggers193
- Iii Http Invoked Functions193
- Iii Node Sdk193
- Iii Trigger Conditions193
- Iii Effect System192
- Iii Reactive Backend192
- Iii Python Sdk190
- Iii Rust Sdk188
- Iii Queue Processing183
- Iii Cron Scheduling180
- Iii Http Endpoints180
- Iii State Management180
- Iii Realtime Streams179