Login Sign Up
Advert
Your ad spot
Reserve this exclusive slot for the selected period.
Buy advertising →
📖 Reference

Errors and Debugging

How to read logs, find and fix errors

Execution Logs

Each automation run creates a log — a record containing all execution details of each node:

  • Status: success or failed
  • Execution time
  • Input and output data
  • Error message (if any)

You can find logs in the "Execution History" section of your automation.

Common Errors and Solutions

❌ «Insufficient balance»

Not enough credits on the balance. Top up your balance on the "Pricing" page.

❌ «Access token missing»

Authorization failure with an external service (Google, Gmail). Reauthorize the account in the "Accounts" section.

❌ «Rate Limit Exceeded»

Too many requests to an external API. Solution: use Batch mode or increase the launch interval.

❌ A node returns empty results

Possible reasons:

  • The source has no new data
  • "Only Unique" is enabled and all data has already been processed. Try a test run — this filter is disabled in test mode
  • Incorrect settings (URL, prompt, etc.)

Single Node Test

The fastest way to debug is to run a test of a specific node. On the canvas, click the "Play" icon right on the node. You will see the logs exclusively for this node without needing to run the whole chain.

💡 Tip: After running a test, open the settings (wrench icon) of the next node and go to the "Data" tab. That is the best place to copy placeholders for use.
← Back to Guide