📝 Overview
Yoom's main function, Flowbot, allows you to test each action even while it's still being developed. We recommend testing all actions before launching it in production.
In this guide, we will explain the common causes of errors during testing and how to resolve them.
1️⃣ Cause Issues with App Integration or Action Settings
Errors can occur during testing if there are mistakes in the app integration or operation settings.
Please verify the following:
Have you registered the application in My Apps correctly?
Are the input values in the correct format as required by the app?
After reviewing these, run the test again.
Exceptions & Notes
If the operation settings are incorrect, a 400-series error code will typically be returned, and Yoom will display an error message accordingly.
However, some apps may return a successful connection even when there’s an error. In these cases, the request may show as successful even if the settings are incorrect.
After testing, double-check that the values are correctly reflected in the app and ensure that the response doesn’t contain error or failure codes.
For most apps, a 400-series error code will be returned in case of an error, and Yoom will display a request failure.
It's important to note that some applications, such as Slack, might indicate a successful request even when an error has occurred.
While each app may have different responses, specifically for Slack, if the first line of the response contains "false," this signifies that the test was unsuccessful. Please be aware of this.
Cause 2: Untested Previous Operations Leading to Incorrect Output Values
If your Flowbot consists of multiple operations and uses output values from earlier operations, the test may fail when the previous operation wasn't tested. This can result in missing or incorrect output values.
Please run the test when setting up each operations to ensure that no retrieved values / output values are left blank.
☝️ Note:
If you don’t save the operation, the test results won’t be saved. Be sure to save after testing.
For example, consider a Flowbot where records are retrieved from a Slack Message and then adds them to Google Sheets.
In this case, please ensure you successfully test the "Retrieve Specific Message from Slack" operation before testing "Add record for Google Sheets." This ensures that when you set up the Google Sheets operation, the retrieved record looks like this:
If the previous operation hasn't been tested, the record-adding operation will have missing output values, potentially leading to an error during testing, like this:
When duplicating a Flowbot, please note that the test results are reset, so this issue is more likely to happen. When duplicating a Flowbot, be sure to test all operations again.
📚 Related Guides
How to Handle Errors in Yoom - View Guide Here
Troubleshooting Errors When Testing a Duplicate Flowbot - View Guide Here
Search Keywords
Search Keywords
Error, Test, Flowbot, Cause, Actions