Troubleshooting Center
Find the likely cause of common workflow, integration, credential, and execution problems.
On this page
Workflow issues
| Problem | Possible cause | How to fix it |
|---|---|---|
| Only one trigger is allowed | A trigger already exists. | Keep one trigger and delete the other. |
| Add exactly one manual trigger before executing | The editor button is being used with no Manual Trigger or a webhook trigger. | Add Manual Trigger for button-run testing, or start webhook workflows from their external service. |
| Trigger must be first | A connection points into the trigger. | Remove the incoming connection and connect outward from the trigger. |
| Variable name must be unique | Two nodes use the same Variable Name. | Rename one node and update downstream templates. |
| Cycle cannot be executed | Connections form a loop. | Remove the loop so dependencies flow forward. |
| Disconnected node never runs | Only nodes reachable from the trigger execute. | Connect the node to the intended path and save. |
Credential issues
| Problem | Possible cause | How to fix it |
|---|---|---|
| Selected credential unavailable | It was deleted, belongs to another user, has the wrong provider, or cannot be decrypted. | Select or create an owned credential of the required provider and save. |
| Encryption not configured | The deployment lacks a valid credential-encryption key. | Contact the deployment administrator; do not paste the secret elsewhere as a workaround. |
| Secret rejected by provider | The key/token is invalid, expired, revoked, or for another application. | Replace the credential from its detail page and retry. |
Telegram, Discord, and Google Forms
- Telegram: Refresh Status, read the last Telegram error, and Update Webhook after any public URL change.
- Discord: confirm Application ID/Public Key, exact command name, required
messageoption, HTTPS reachability, and the current endpoint-discovery limitation. - Google Forms: submit through the form—not Apps Script's Run button—check the installed trigger, current
WEBHOOK_URL, and one-time secret. - For every webhook integration, a stale local tunnel URL prevents the external service from reaching NexFlow.
AI and HTTP issues
- Gemini quota, invalid key, or unavailable model messages are safe provider summaries. Correct the credential/model or retry later.
- A template error usually means the variable is misspelled, not upstream, or the property path is wrong.
- HTTP failures include status and bounded context, while response bodies and common secret patterns are removed from execution history.
- HTTP Request intentionally blocks private/internal addresses; expose a suitable public endpoint instead of trying to bypass the restriction.
Execution issues
- Pending means queued but not started. Refresh Executions and allow the asynchronous worker time to claim it.
- If queuing fails, NexFlow marks the execution Failed with
Workflow execution could not be queued. - A running editor execution disables Save and Execute to avoid overlapping changes.
- Use the execution detail's first failed node, not only the final workflow status, to locate the cause.