Possible errors in nodes
Common errors and troubleshooting solutions.
Usually, the cause of an error is clearly stated at the bottom of the error message. For example, in the error:
exec command error: request to pd server
code 500
error: ETELEGRAM: 400 Bad Request: chat not found
The "400 Bad Request: chat not found" part indicates that the issue is likely due to an incorrect or missing chat ID. Always check the last lines of the error message for clues on what went wrong.
HTTP Error Codes
These errors occur when making HTTP requests.
Client Errors (4xx)
- 400 Bad Request – Invalid request (incorrect data format, missing parameters).
- 401 Unauthorized – Authentication error (wrong API key, token, login/password).
- 403 Forbidden – Access denied (insufficient permissions, IP restrictions).
- 404 Not Found – Requested resource not found (wrong URL or deleted object).
- 405 Method Not Allowed – The request method (GET, POST, PUT, etc.) is not supported by the server.
- 408 Request Timeout – The server did not receive a response in time.
- 429 Too Many Requests – Request limit exceeded (Rate Limit Exceeded).
Server Errors (5xx)
- 500 Internal Server Error – Unexpected server failure.
- 502 Bad Gateway – Proxy or gateway issue (e.g., API server is down).
- 503 Service Unavailable – The external service is overloaded or temporarily unavailable.
- 504 Gateway Timeout – The server did not respond in time.
JavaScript Error Codes
These errors occur when executing code inside nodes.
- SyntaxError – Syntax error (e.g., missing bracket or comma).
Authentication Errors
These errors occur when connecting to services using OAuth 2.0.
- invalid_request – Invalid parameters in the OAuth request.
- invalid_client – Incorrect client identifier (Client ID).
- invalid_grant – Invalid authorization code or refresh token.
- unauthorized_client – The client does not have permission to access.
- access_denied – The user denied the authorization request.
- unsupported_grant_type – Unsupported authorization request type.
Webhook Errors
If your webhook suddenly stops receiving requests, even though it previously worked fine, and you can’t identify the cause — try opening the webhook URL directly in your browser.
If you see the following error message:
building js code is failed: Node build fatal errorIt means that there is invalid JavaScript code in one of your scenario’s nodes. Most likely, recent changes introduced code that can’t be compiled.
This error occurs during the build phase, before the scenario even starts running — which is why you won’t see it in the execution history