This reference covers the most common issues encountered when building and running bots on Narakim.
Logic Canvas Issues
| Problem | Likely Cause | Solution |
|---|
| Extension not in Node Palette | Not installed | Go to Extensions tab → install it |
| Node shows a red validation error | Missing required config field | Click the node → fill in all required fields in the Config Sidebar |
| Edge shows type mismatch | Source output type ≠ target input type | Open the Mapping Panel → verify type compatibility or add a Transform |
| "Graph has cycles" error on save | A → B → A loop exists | Remove one of the edges creating the cycle |
| "No trigger node" error | The automation has no trigger | Add a trigger node and designate it as the primary trigger |
Deployment Issues
| Problem | Likely Cause | Solution |
|---|
Bot stuck in STARTING | Missing required secrets | Go to Configurations → fill in all required secret fields |
Bot enters ERROR immediately | Invalid automation definition | Re-run Validate Graph on the Logic canvas; check the log stream for the specific error |
Platform connection shows ERROR | Invalid bot token or expired credentials | Go to Configurations → Platform Connections → click Reconnect or re-enter credentials |
404 Unknown Channel in Discord | Wrong ID type used | Ensure channelId is a channel snowflake, not a user ID. Use Send DM for user IDs |
| Discord interactions not responding | Interaction response timeout | Use Reply to Interaction within 3 seconds. Use Defer Interaction if processing takes longer |
Data & Template Issues
| Problem | Likely Cause | Solution |
|---|
| Template string returns literally (not resolved) | Path is incorrect | Enable LOG_LEVEL=debug in deployment env vars to see resolution attempts |
| Node config field not accepting template strings | Field is not in "Template Input" mode | Look for the { } toggle icon in the config field to switch to template mode |
undefined value in execution | Mapped field doesn't exist on the source node | Check the source node's output schema; the field name may be different than expected |
| ForEach not iterating | Input is not an array | Ensure the upstream node produces an array at the mapped path; use Transform Data to wrap if needed |
Discord-Specific Issues
| Problem | Likely Cause | Solution |
|---|
| Bot not receiving messages | MESSAGE_CONTENT intent not enabled | Go to Discord Developer Portal → Bot section → enable MESSAGE_CONTENT privileged intent |
| Slash commands not appearing | Commands not registered | Use the Register Slash Command action node to register commands with Discord's API |
| Button click not triggering automation | No Button Click trigger node | Add a Button Click trigger; ensure customId matches the button's defined custom ID |
| Modal not submitting | No Modal Submit trigger | Add a Modal Submit trigger; map interactionToken from the show-modal action |
Secrets Issues
| Problem | Likely Cause | Solution |
|---|
| "Missing required secret" on deploy | Secret not configured | Go to Configurations → Extension Secrets → fill in the required value |
| Secret appears to be wrong | Stale value / typo at entry | Overwrite the secret with the correct value — secret fields accept new values at any time |
| Extension works in development but not production | Different secrets configured per environment | Check that the production secret is configured in the Configurations tab under the PRODUCTION environment |
Getting More Help
If the issue is not covered here:
- Check the Log Stream in the Deployments tab for the specific error message and execution trace.
- Enable
LOG_LEVEL=debug in your deployment environment variables for verbose output.
- Open the AI Agent Studio and paste the error message — the AI will diagnose and suggest a fix.
- Contact support via the in-app chat.
historyLast updated: May 10, 2026
