# Troubleshooting (/docs/reference/troubleshooting)

Solutions for the 10 most common issues.



1\. Workflow won't save [#1-workflow-wont-save]

**Cause**: Network connectivity issue or session expiration.

**Fix**: Check your internet connection. Refresh the page and try saving again. If the issue persists, copy your node configuration and reload.

2\. Node shows credential error after adding credentials [#2-node-shows-credential-error-after-adding-credentials]

**Cause**: The node isn't linked to the credential, or the key is invalid.

**Fix**: Click the node, open settings, and select your credential from the **Parameters** pane. If already selected, re-open the credential in [Credentials](/docs/credentials) and verify the key is correct.

3\. Cron trigger not firing [#3-cron-trigger-not-firing]

**Cause**: Schedule is disabled, or plan doesn't support the frequency.

**Fix**: Check the **Activate** / **Active** control in the editor toolbar. <PlanName plan="free" /> plan only supports daily/weekly crons. Verify the cron configuration in the trigger node.

4\. Webhook not receiving requests [#4-webhook-not-receiving-requests]

**Cause**: Workflow not enabled, or incorrect URL.

**Fix**: Click **Activate** in the editor toolbar. Verify the URL includes the correct `workflowId` and `token` parameters. Test with curl.

5\. DeFi node failing with API error [#5-defi-node-failing-with-api-error]

**Cause**: Rate limiting, invalid parameters, or service outage.

**Fix**: Check the error message in the executions panel or run detail sheet. Use the failed-node filter or node mini-map to jump to the failing node. Common causes: invalid token address, amount too small for swap, API rate limit. Try again after a few seconds.

6\. Marketplace purchase succeeded but workflow not in dashboard [#6-marketplace-purchase-succeeded-but-workflow-not-in-dashboard]

**Cause**: Transaction confirmed but clone not yet visible.

**Fix**: Purchases are normally fulfilled immediately after on-chain confirmation. If the confirmation timed out during checkout, a background recovery job will complete it within a few minutes. Refresh your dashboard. Check the Wallet page to confirm the payment status.

7\. SOL balance not updating [#7-sol-balance-not-updating]

**Cause**: Balance is fetched from the Solana network and may have a short cache.

**Fix**: Refresh the wallet page. Recent transactions may take a few seconds to reflect.

8\. Can't connect wallet [#8-cant-connect-wallet]

**Cause**: Embedded wallet not created yet or browser issue.

**Fix**: Solaris AI Flow creates an embedded Privy wallet automatically on sign-up. If your wallet isn't showing, try signing out and back in. Clear browser cache and retry. If the issue persists, check that third-party cookies are not blocked for the Privy auth domain.

9\. Execution stuck in "running" state [#9-execution-stuck-in-running-state]

**Cause**: The execution action crashed mid-flight.

**Fix**: Stuck executions are automatically cleaned up after 10 minutes and marked as failed. No manual intervention needed.

Next steps [#next-steps]

* [FAQ](/docs/reference/faq) - general questions
* [Error Handling](/docs/executions/errors) - execution-level errors