Creating Processes: -Troubleshooting

Crashing REST API Step:

When using API Steps within Symphona, here are the most common error codes you might run into:

400 (Bad Request)

Check your request format, parameters, and JSON syntax
Verify all required fields are included and properly formatted
Ensure data types match API specifications

401 (Unauthorized)

Confirm your API key or authentication credentials are valid
Check that credentials are correctly entered (no extra spaces or characters)
Verify your API key hasn't expired

403 (Forbidden)

Verify you have the necessary permissions to access the endpoint
Check your subscription level or plan includes access to this resource
Ensure your account is in good standing

404 (Not Found)

Double-check the API endpoint URL for typos
Verify you're using the correct API version
Confirm the resource you're requesting actually exists

429 (Too Many Requests)

Implement rate limiting within your process
Use exponential backoff strategies for retries
Check the API's rate limit documentation and adjust your request frequency

500 (Internal Server Error)

The issue is on the API provider's side
Wait and retry after a few minutes
Check the API provider's status page for known outages

502 (Bad Gateway) / 503 (Service Unavailable)

API service is temporarily down or overloaded
Turn on retry or increase the delay time
Monitor the provider's status page

504 (Gateway Timeout)

Your request took too long to process
Consider breaking large requests into smaller chunks

Prompt AI:

When using Prompt AI, the same rules apply for the rest of our platform. For more information, follow this guide.

Dynamic Parameters:

It can sometimes be tricky to get your parameters to be read by our platform. In the case that the highlighted parameter is not read by your process correctly. Try using the parameter name without highlighting. Our system understands that it is a variable and not plain text. In this example, we want to sanitize our Address, if it is null or length of 0, set it to Unavailable. If it exists, leave it:

Address == null || Address == '' || Address.length == 0 ? "Unavailable" : "Address"

In this case, only the second address is a highlighted parameter, the first one is written normally, but it is properly read by our system.

When using numbers within Symphona, our system can automatically convert a string of numbers to a number type variable, even if set to type “Anything”. To get around this, use the .toString() method to convert the numbers before further manipulation. This can be important for comparison within Conditional Branches,

Set Parameter Value:

Within the Set Parameter Value step, try to avoid using the “:” character within your message. This is because our back end system reads the : as code, and will sometimes end your message or variable earlier than you would like.