• TRIAGE
  • REPAIR
  • DATA
  • HUMAN

How to troubleshoot automation failures with your AI

Connect Hexomatic to your agent to turn messy execution logs into clear answers. Your AI handles the heavy lifting of scanning through run histories to find the root cause of a crash.

Ask AI about this page

Short answer

How do I find out why my Hexomatic automation failed?

Your agent uses the Hexomatic MCP to pull execution logs and list your existing workflows. It then analyzes the error data to tell you if a selector changed, a site blocked you, or a lead was missing. You get a direct explanation of the failure and a path to fix it.

Troubleshooting outcomes

Where every issue lands.

The AI categorizes failures so you know exactly what needs your attention.

TRIAGE

Error identification

The agent scans logs to find the specific error message. You get a plain English explanation of what went wrong.

REPAIR

Fixing broken selectors

The AI identifies if a web scraping run failed because a website changed its structure. It points you to the exact element that broke.

DATA

Missing lead info

If a lead generation run stops, the agent checks if the data was missing or blocked. You'll see if the source data was actually there.

HUMAN

Manual intervention

When the logs show a CAPTCHA or a hard block, the agent flags it for you. You decide how to bypass the restriction manually.

The workflow

What your AI does when <the thing arrives>.

Instead of you scrolling through thousands of lines of JSON, your agent does the digging.

  1. Locate the workflow

    The agent identifies which specific automation you are worried about by looking at your active setups.

    list_workflows
  2. Pull the logs

    The agent fetches the raw execution data for the failed run to see the exact moment the process stopped.

    get_execution_logs
  3. Analyze the error

    The agent parses the log data to separate network timeouts from actual scraping errors.

    get_execution_logs
  4. Report the cause

    The agent summarizes the findings so you can decide whether to update a selector or change a proxy.

    get_execution_logs

Try it

Copy these to start.

Use these prompts to kick off the troubleshooting process.

Starting points

Replace the specific workflow names or run IDs with your actual Hexomatic details.

Hexomatic Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_ReTF3G4BgcGresVEgq0YHr8NQJVt04f7REqfsFkI/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Hexomatic capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "hexomatic-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_ReTF3G4BgcGresVEgq0YHr8NQJVt04f7REqfsFkI/mcp"
    }
  }
}
Copy into chat04
  • Why did my 'LinkedIn Lead Gen' workflow fail during its last run?

  • Check the execution logs for my 'Amazon Scraper' and tell me if it's a timeout issue.

  • List my Hexomatic workflows and find the one that errored out most recently.

  • Look at the logs for the last lead generation run and tell me why the data extraction failed.

  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Start here

Connect Hexomatic once, then ask.

One quick connection links your Hexomatic account to your agent. Your credentials stay encrypted, and you can start asking questions immediately.

Connect Hexomatic to your AI

FAQ

How this task behaves.

  • 01

    Can the AI fix the broken scraper for me?

    No. The AI identifies the error and tells you what changed, but you have to go into Hexomatic to update the selectors or settings yourself.

  • 02

    Can the AI start a new run if one fails?

    No. This MCP is designed to read logs and list workflows, not to trigger or execute new automation runs.

  • 03

    Does the AI see all my Hexomatic data?

    The AI only sees the workflow lists and the specific execution logs you ask it to inspect.

  • 04

    Can the AI delete a failed workflow?

    No. The agent can only read data from your workflows and logs; it cannot modify or delete your Hexomatic setups.

  • 05

    How does it know which run failed?

    It uses the execution logs to find entries with error statuses or failed completion flags.

  • More questions about Hexomatic? The Connector page answers them. See everything the Hexomatic Connector can do

Connect Hexomatic to Claude, Cursor, ChatGPT & more