Even the most carefully designed workflows can encounter errors. Keragon provides detailed logs and intuitive debugging tools to help you quickly identify and resolve these issues. This guide covers the most frequent errors you may face and how to fix them efficiently.
1. Authentication Errors
-
Cause: The connected app account is invalid, expired, or missing required permissions.
-
How to Resolve:
-
Go to the Auth tab of the affected step.
-
Reconnect or refresh the authentication.
-
Ensure the connected account has the required permissions for the action.
-
Example: An action fails to send an email because the Gmail account token has expired.
2. Missing Required Inputs
-
Cause: One or more required fields are empty or not properly mapped.
-
How to Resolve:
-
Review the Inputs tab of the step.
-
Ensure all mandatory fields are filled with static values or mapped variables.
-
Use the Variable Selector to confirm that the expected data is available.
-
Example: A CRM integration fails because the required "Email" field was left empty.
3. Invalid Data Formats
-
Cause: The data being passed does not match the required format (e.g., wrong date format, non-numeric values in a numeric field).
-
How to Resolve:
-
Validate data types using Keragon’s Data Formatting Helpers before passing them to actions.
-
Use the Transform/Convert Datetimes helper for date formats and Text to Number helper for numeric conversions.
-
Example: An API request fails because the date format is MM/DD/YYYY instead of the required YYYY-MM-DD.
4. API Rate Limits and External System Failures
-
Cause: External services impose limits on API usage or are temporarily unavailable.
-
How to Resolve:
-
Check the API rate limits in the service’s documentation.
-
Implement retry mechanisms where possible.
-
Use the Delay action to introduce wait times and reduce request bursts.
-
Example: A Salesforce API call fails with a 429 "Too Many Requests" error.
5. Incorrect Conditional Logic
-
Cause: The logic used in Branch or Continue If actions does not match the expected conditions, causing unexpected behavior.
-
How to Resolve:
-
Review the conditions and ensure correct comparison operators are used.
-
Check the actual values of variables using the Test Step feature.
-
Example: A workflow stops unexpectedly because the value comparison uses equals instead of contains.
6. Empty or Null Data Returned
-
Cause: A previous step didn’t produce the expected output, leaving no data for downstream actions.
-
How to Resolve:
-
Use the Test Step function to verify the output of each step.
-
Add fallback values using the Fallback Value helper.
-
Example: An email is not sent because the recipient list was empty due to a failed API response.