How to Find Make.com Scenario Errors (A 2-Minute Weekly Check)

Let ChatGPT check your Make account for broken automations. Try TinyFish free. New accounts start with $8 in Wallet funds.

TL;DR

Make.com scenario errors are easy to miss. A scenario fails on Tuesday, nobody opens the History tab, and on Friday a customer asks why they never got their invoice. This guide shows a weekly health check you can run in about two minutes of your time: ask ChatGPT or Claude, with the TinyFish app connected, to list every failed run from the last few days with the failing step and the error message. It reads only. It doesn't edit or rerun anything.

A quick disclosure: I work at TinyFish, which gives ChatGPT and Claude live web access, including a browser agent that can click through real websites for you.

Why a weekly check

If you're a team of one to five, Make is probably doing a job someone used to do by hand: copying orders into a sheet, sending a welcome email, posting new leads to Slack. When it works, you forget about it. When it breaks, you find out late.

Checking each scenario's history yourself means opening every scenario, one at a time. Most weeks you'll find nothing. That's exactly why it's easy to skip, and why it's a good job to hand off.

Where Make.com scenario errors show up

Two places in Make matter for this, both from Make's own help center:

• The History tab on each scenario lists its runs with a date and time, a status (Success, Warning or Error), the run duration and a Details link that opens the log (Make: Scenario history). How many days of history you get depends on your Make plan.
• The Incomplete executions tab holds runs that stopped partway and were saved so you can finish them later. Make notes that temporary errors such as ConnectionError or RateLimitError can usually be retried, while errors like RuntimeError and DataError usually need a fix in the module first (Make: Manage incomplete executions).

The prompt below asks the agent to collect what those pages already show, across your account, in one list.

What you need

• ChatGPT or Claude with the TinyFish app. Install it once by following the plugin docs. After that you ask in plain English, and TinyAgent opens the site in a real cloud browser and reports back.
• A saved Make login in TinyProfiles. You sign in to Make once in a secure TinyFish browser profile. Later tasks reuse that signed-in session, so the agent skips the login. TinyFish never needs your password in the chat. If the profile isn't signed in, the agent stops and asks you to sign in.

The prompt

This is the exact prompt our engineering team tested. Replace [N] with the number of days you want to look back:

Use my saved login to check my Make account for errors. List failed runs from the last [N] days with the failing step and error message. Read-only: don't edit or rerun anything.

Filled in for a weekly Monday check:

Use my saved login to check my Make account for errors. List failed runs from the last 7 days with the failing step and error message. Read-only: don't edit or rerun anything.

If one scenario is noisy, narrow it down:

Use my saved login to check my Make account for errors in the scenario "Shopify orders to Google Sheets" only. List failed runs from the last 3 days with the failing step and error message. Read-only: don't edit or rerun anything.

Why read-only matters

Your scenarios are live. Rerunning a failed run can send the same email twice or create a duplicate order row. Editing a module can break the runs that were working. So the prompt asks the agent to look and report, nothing else.

That makes the check safe to run any time, even in the middle of a busy sales week. You decide what to fix, and you fix it in Make.

What you get back

A list of failed runs, grouped by scenario. For each one, expect:

• Scenario name
• When it failed: date and time of the run
• Failing step: the module where it stopped, for example a Google Sheets or Gmail module
• Error message: the text Make shows for that run

If nothing failed, it says so. That's the result you want most weeks.

Example output (invented business)

For this invented bakery, both errors point to a fix you make once: reconnect Google Sheets, and update the Slack channel after someone renamed it.

Tips

• Start with 7 days. A week is a natural rhythm. If your history is long and the answer comes back cut short, ask for 3 days, or one scenario at a time.
• Ask a follow-up. Once you have the list, ask ChatGPT what a given error message usually means. Make also has its own Explain error option inside each run's log.
• Fix it yourself in Make. Open the scenario's History or Incomplete executions tab and use the Details link for the full log.
• Put it on your calendar. Same prompt, same day each week. Two minutes, and you hear about broken automations before your customers do.

When it doesn't work

• It can't start, or says it isn't signed in. This is the most common reason a check fails to start. Your TinyProfile isn't signed in to Make, or the session expired. Sign in again in the profile and rerun.
• The list looks short. Long histories can come back partial. Ask for fewer days or one scenario.
• The run you remember isn't there. Make keeps history for a set number of days depending on your plan. Older runs may be gone.
• ChatGPT asks about a step limit first. That's normal. Confirm and let it start.

Want to see this live? We're running it at TinyFish Small Business Week, a free 45-minute live session on Thu Nov 19, 11 AM ET. Save your seat, and bring the job you want off your plate.

Hear about broken automations before your customers do. Start free on TinyFish.