May 1, 2024

How to Troubleshoot Scenarios logo

Troubleshooting (formerly Integromat) scenarios can often seem daunting, but with a systematic approach, you can quickly identify and resolve most issues. Here's how to tackle problems you may encounter with your automations.

Step 1: Check the Scenario Log

The scenario log is your first stop for troubleshooting. It contains detailed information about each operation within a scenario.

  • Access the Log: Go to the scenario with issues and click on the "History" tab to review the logs.
  • Review Errors: Look for any modules with red exclamation marks, which indicate errors. Click on the error message to view more details.

Step 2: Examine Each Module

A scenario's failure can often be traced to a single module. Carefully check each one to ensure:

  • Correct Configuration: Verify that all necessary fields are filled out correctly.
  • Authorization: If the module connects to an external service, make sure the authorization hasn't expired.

Step 3: Validate Data Formats and Types

Data mismatches are common culprits in scenario hiccups.

  • Check Data Types: Make sure that the data passed between modules matches the expected types (e.g., string, integer, date).
  • Inspect Data Formats: Confirm that data formats adhere to the required structures (e.g., JSON objects, arrays).

Step 4: Test with Sample Data

If everything seems to be configured correctly yet still fails, conduct a test with sample data.

  • Isolate the Issue: Temporarily disable all modules except for the one you suspect is causing the issue.
  • Run a Test: Use the "Run once" feature with sample data to see if the module performs as expected.

Step 5: Check External Services

Sometimes the issue lies not within but with one of the connected services.

  • Service Status: Check if the external service is experiencing any outages or known issues.
  • API Limitations: Be aware of any API call limits that could be preventing the scenario from completing.

Step 6: Examine Delays and Scheduling

Delays in execution can lead to scenarios not running when you expect them to.

  • Scheduling: Verify the scenario schedule settings are as intended.
  • Delay Settings: Look at any delay functions or wait times you have set up within your scenario.

Step 7: Reach Out to Support

If after all these steps the problems persist, seek further help.

  • Support: Use the in-app support or the community forums to seek advice from the team or peers.
  • Documentation: Reference's detailed documentation for in-depth guidance on specific modules or functions.

By following these steps, you should be able to effectively troubleshoot most issues in your scenarios. Remember, patience and methodical testing are keys to resolving automation complexities.