Your email automation ran perfectly for three weeks. Then it stopped sending notifications. Your customer data sync broke. Your social media posts aren't publishing. You check your automation platform, and you see red error messages you don't understand. You're not a developer. You don't know where to start.
This happens to thousands of small business owners every month. They build their first automation, it works beautifully, then it breaks. The good news? Most automation failures are caused by the same five issues. Once you know how to identify them, you can fix 80% of problems yourself in under 30 minutes.
Quick Win: 80% of automation failures come from five common causes: expired API keys, rate limits, changed app interfaces, missing permissions, and data format changes. Learn to spot these, and you'll fix most issues without technical help.
Automation debugging doesn't require coding skills. It requires a systematic approach. This guide walks you through a step-by-step troubleshooting process that works for any automation platform—Make.com, n8n, Zapier, or others. You'll learn how to read error messages, identify the problem, and apply the right fix.
By the end, you'll know exactly when to restart your automation, when to rebuild it, and when to ask for help. You'll also learn how to set up simple monitoring so you catch problems before they impact your business.
Common Signs Your Automation Is Broken
Before diving into debugging, you need to recognize when something's wrong. Automation failures aren't always obvious. Sometimes your automation runs but produces no results. Other times, it fails silently.
No notifications or outputs: Your automation should send emails, create records, or update spreadsheets. If these outputs stop appearing, your automation likely failed. A 10-person marketing agency noticed their lead qualification automation stopped sending Slack notifications. The automation was still running, but the Slack integration had disconnected.
Missing data in expected locations: Your automation should populate specific fields, create files, or update databases. When data doesn't appear where it should, check your automation. A small e-commerce store automated order confirmations to their CRM. Orders were processing, but customer records weren't updating. The automation was failing at the CRM step.
Error messages in your automation platform: Most platforms show error indicators when something breaks. Red badges, warning icons, or failed execution statuses are clear signs. Don't ignore these. They tell you exactly where the problem occurred.
Automation runs but produces incorrect results: Sometimes automations execute successfully but generate wrong outputs. Duplicate records, incorrect data formatting, or missing information indicate a problem. A consulting firm's automation created duplicate invoices for every customer. The automation ran, but the logic was wrong.
Automation doesn't trigger at all: Your automation should start automatically when certain conditions are met. If it never runs, the trigger isn't working. Common causes include changed trigger conditions, disconnected services, or disabled automations.
Reality Check: Most business owners discover automation failures 2-3 days after they occur. By then, you've lost data, missed opportunities, or annoyed customers. Set up basic monitoring to catch problems within hours, not days.
Step-by-Step Debugging Process
Debugging automation follows a logical sequence. Start with the most common issues and work your way through systematically. This process works for any automation platform and any type of automation.
Step 1: Check Execution Logs and History
Every automation platform keeps a history of executions. This is your first stop when something breaks. Logs show you exactly when your automation ran, what happened at each step, and where it failed.
How to access logs:
- Make.com: Go to your scenario, click "Runs" in the left sidebar, and review execution history
- n8n: Click on your workflow, then check the "Executions" tab at the bottom
- Zapier: Open your Zap, scroll to "Task History" to see recent runs
What to look for:
- Red error indicators or failed status badges
- Execution times (if they're unusually long, something might be timing out)
- Error messages at specific steps
- Last successful run date (if it's been days, the automation stopped working)
Real-world example: A real estate agency's automation stopped creating new listings. They checked the logs and found the automation was failing at step 3 (Google Sheets update). The error message said "Permission denied." They fixed the Google Sheets permissions, and the automation worked again.
Step 2: Verify API Connections and Credentials
Most automation failures come from broken connections. Your automation connects to external services (Gmail, Slack, Google Sheets, CRM systems) using API keys or OAuth tokens. These connections expire, get revoked, or break when services update their security.
How to check connections:
- Open your automation platform
- Navigate to the step that's failing
- Look for connection status indicators (usually a green checkmark or red X)
- Click "Reconnect" or "Test Connection" if available
Common connection issues:
- Expired tokens: OAuth tokens expire after 30-90 days. You'll need to re-authenticate
- Revoked permissions: If you changed your password or security settings, connections may break
- Service updates: When services like Google or Microsoft update their APIs, old connections stop working
Quick fix: Most platforms let you reconnect with one click. If reconnecting doesn't work, you may need to remove the connection and create a new one.
Pro Tip: Set calendar reminders to check your automation connections every 60 days. Most OAuth tokens expire around this time. A 5-minute check prevents hours of debugging later.
Step 3: Test Each Step Individually
When your automation has multiple steps, the failure could be at any point. Testing each step individually helps you pinpoint exactly where the problem occurs.
How to test steps:
- Start with the first step (usually the trigger)
- Manually trigger it or use test data
- Check if it produces the expected output
- Move to the next step and repeat
- Stop when you find the step that fails
Platform-specific testing:
- Make.com: Use the "Run once" feature to test individual modules
- n8n: Click the "Execute Workflow" button and watch each node process
- Zapier: Use "Test this Zap" to run through each step
What you're looking for:
- Steps that produce no output
- Steps that produce incorrect output
- Steps that timeout or take too long
- Error messages at specific steps
Real-world example: A content agency's automation had 8 steps. It was failing somewhere in the middle, but they didn't know where. They tested each step individually and discovered step 5 (formatting data for the CRM) was receiving data in the wrong format. They fixed the data mapping, and the automation worked.
Step 4: Check for Data Format Changes
Services update their data formats regularly. What worked last month might not work today. When APIs change, your automation might receive data in a different structure than expected.
How to identify format changes:
- Compare current data output with what your automation expects
- Look for new fields, removed fields, or renamed fields
- Check if data types changed (text to numbers, dates to timestamps)
- Review recent service updates or changelogs
Common format changes:
- Field name changes: "first_name" becomes "firstName" or "firstname"
- Data type changes: Dates change from "2025-01-28" to Unix timestamps
- Nested data: Previously flat data becomes nested objects
- Required fields: New required fields that your automation doesn't provide
How to fix:
- Update your automation to match the new data format
- Use data transformation steps to convert formats
- Contact the service provider if changes are undocumented
Step 5: Verify Trigger Conditions
Your automation starts when certain conditions are met. If those conditions change or become invalid, your automation won't trigger.
How to check triggers:
- Review your trigger settings
- Verify the conditions are still valid
- Test the trigger manually if possible
- Check if the source data/service still exists
Common trigger issues:
- Changed folder names: If your trigger watches a specific folder and you renamed it, the trigger breaks
- Deleted webhooks: If you're using webhooks and the endpoint was deleted, triggers stop
- Modified filters: If your trigger has filters and the data no longer matches, nothing triggers
- Disabled services: If the source service is disabled or deleted, triggers fail
Real-world example: A law firm automated document processing from a specific Dropbox folder. They renamed the folder for organization, and the automation stopped triggering. They updated the trigger to watch the new folder name, and it worked again.
Step 6: Review Error Messages Carefully
Error messages contain valuable information, but they're often written in technical language. Learning to read them helps you fix problems faster.
How to read error messages:
- Look for the error type (authentication, rate limit, data format, etc.)
- Identify which step failed (usually mentioned in the message)
- Note any specific error codes or references
- Check the error message against common issues
Common error types and what they mean:
- "401 Unauthorized" or "Authentication failed": Your API key or token expired or is invalid
- "429 Too Many Requests" or "Rate limit exceeded": You're making too many requests too quickly
- "404 Not Found": The resource (file, record, endpoint) doesn't exist
- "400 Bad Request": The data you're sending is in the wrong format
- "500 Internal Server Error": The service you're connecting to has a problem (usually temporary)
- "Connection timeout": The service took too long to respond
Step 7: Test with Sample Data
Sometimes automations work with test data but fail with real data. Testing with actual data helps you catch real-world issues before they impact your business.
How to test with real data:
- Use a small sample of actual data (not test data)
- Run your automation with this sample
- Verify outputs match expectations
- Check for edge cases (empty fields, special characters, unusual formats)
What to test:
- Data with missing optional fields
- Data with special characters or formatting
- Data at the limits (very long text, very large numbers)
- Data with unexpected formats (dates in different formats, phone numbers with/without country codes)
How to Read Error Messages in Plain English
Error messages are written for developers, not business owners. Here's how to translate the most common ones into plain English.
"401 Unauthorized" or "Invalid credentials":
- What it means: Your login credentials (API key, password, token) are wrong or expired
- What to do: Reconnect the service or update your API key
- Time to fix: 2-5 minutes
"429 Too Many Requests" or "Rate limit exceeded":
- What it means: You're making requests too quickly. The service is limiting you to prevent overload
- What to do: Wait 15-60 minutes, or reduce how often your automation runs
- Time to fix: Usually resolves automatically, but you may need to adjust automation frequency
"404 Not Found":
- What it means: The file, record, or resource your automation is looking for doesn't exist
- What to do: Check if the resource was deleted, moved, or renamed. Update your automation to point to the correct resource
- Time to fix: 5-10 minutes
"400 Bad Request":
- What it means: The data you're sending is in the wrong format or missing required information
- What to do: Check your data mapping. Ensure all required fields are included and formatted correctly
- Time to fix: 10-30 minutes depending on complexity
"500 Internal Server Error":
- What it means: The service you're connecting to has a problem on their end (not your fault)
- What to do: Wait 15-30 minutes and try again. If it persists, check the service's status page
- Time to fix: Usually resolves automatically within an hour
"Connection timeout":
- What it means: The service took too long to respond, so your automation gave up waiting
- What to do: Check your internet connection. If it's stable, the service might be slow. Try again
- Time to fix: Usually works on retry
Key Insight: Most error messages point to one of five problems: authentication, rate limits, missing resources, data format issues, or service outages. Once you learn these patterns, you can diagnose 90% of errors quickly.
Quick Fixes for the Most Common Issues
These five issues cause 80% of automation failures. Learn to fix them, and you'll resolve most problems yourself.
Issue 1: Expired API Keys
How to identify: Error messages like "401 Unauthorized," "Invalid credentials," or "Authentication failed"
How to fix:
- Go to the service's settings (where you got the API key originally)
- Check if the key is still active
- If expired, generate a new API key
- Update your automation with the new key
- Test the connection
Prevention: Set calendar reminders to check API keys every 60-90 days. Most keys expire around this time.
Real-world example: A marketing agency's automation stopped syncing leads to their CRM. The error said "401 Unauthorized." They checked their HubSpot API key and found it expired 3 days earlier. They generated a new key, updated their automation, and it worked immediately.
Issue 2: Rate Limits
How to identify: Error messages like "429 Too Many Requests," "Rate limit exceeded," or "Quota exceeded"
How to fix:
- Check how often your automation runs
- Reduce the frequency if it's running too often
- Wait 15-60 minutes for the limit to reset
- Consider upgrading your service plan if you need higher limits
Prevention: Understand your service's rate limits before building automations. Most free plans have strict limits (100-1,000 requests per day). Paid plans offer higher limits.
Real-world example: A small business automated social media posting every 15 minutes. After a week, they hit Twitter's rate limit. They reduced posting frequency to every hour, and the automation worked again.
Issue 3: Changed App Interfaces
How to identify: Automation works but produces incorrect results, or specific steps fail with "field not found" errors
How to fix:
- Check the service's changelog or update notes
- Review your automation's field mappings
- Update field names to match the new interface
- Test with sample data to verify
Prevention: Subscribe to update notifications from services you automate. Most services announce breaking changes 30-60 days in advance.
Real-world example: Google Sheets updated their API, and a consulting firm's automation stopped updating specific columns. The column names changed from "First Name" to "firstName." They updated the field mappings, and the automation worked.
Issue 4: Missing Permissions
How to identify: Error messages like "Permission denied," "Access forbidden," or "Insufficient permissions"
How to fix:
- Check the service's permission settings
- Ensure your automation has the required permissions
- Re-authenticate if permissions were revoked
- Contact the service provider if permissions seem correct but still fail
Prevention: When setting up automations, grant the minimum permissions needed. Over-permissioning can cause security issues, but under-permissioning causes failures.
Real-world example: A real estate agency's automation couldn't create new listings in their CRM. The error said "Permission denied." They checked their CRM permissions and found the automation account only had "read" access. They upgraded to "write" access, and the automation worked.
Issue 5: Data Format Changes
How to identify: Automation runs but produces incorrect or missing data, or errors about "invalid format"
How to fix:
- Compare current data structure with what your automation expects
- Update data mappings to match new formats
- Add data transformation steps if needed
- Test with sample data to verify
Prevention: Use data validation steps in your automation to catch format changes early. Most platforms offer "filter" or "validate" steps you can add.
Real-world example: A content agency's automation stopped formatting customer names correctly. The CRM changed name fields from separate "First" and "Last" to a single "Full Name" field. They updated their automation to split the full name, and it worked again.
When to Restart vs. Rebuild an Automation
Not every broken automation needs a complete rebuild. Sometimes a simple restart or reconnection fixes the issue. Here's how to decide.
Restart your automation when:
- A single step fails due to a temporary issue (service outage, network problem)
- Connections expired but are easy to reconnect
- Data format changed slightly and can be fixed with simple mapping updates
- The automation logic is still correct, but execution failed
Rebuild your automation when:
- Multiple steps are failing consistently
- The service you're automating changed significantly (major API update, new interface)
- Your business process changed, and the automation no longer matches your workflow
- The automation was built incorrectly from the start
Decision framework:
- Count the failing steps: If 1-2 steps fail, restart. If 3+ steps fail, consider rebuilding
- Check service updates: If the service had a major update, rebuilding might be faster
- Assess time investment: If fixing takes more than 2-3 hours, rebuilding might be more efficient
- Review business needs: If your process changed, rebuild to match new requirements
Reality Check: Most business owners try to fix broken automations for hours when rebuilding would take 30 minutes. If you've spent more than 2 hours debugging without progress, rebuilding is usually faster. Start fresh with what you learned from the failure.
Real-world example: A marketing agency's automation had 5 failing steps after a major CRM update. They spent 4 hours trying to fix each step. Finally, they rebuilt the automation in 45 minutes using the new CRM interface. The rebuild was faster and more reliable.
How to Set Up Simple Monitoring
Catching automation failures early prevents data loss and customer issues. You don't need complex monitoring tools. Simple checks work for most small businesses.
Platform-built monitoring: Most automation platforms offer basic monitoring:
- Make.com: Set up email notifications for failed scenarios
- n8n: Use webhooks to send alerts to Slack or email when workflows fail
- Zapier: Enable error notifications in your Zap settings
What to monitor:
- Execution status: Did your automation run when expected?
- Error rates: How often does your automation fail?
- Output verification: Are the expected outputs being created?
- Data quality: Is the data correct and complete?
Simple monitoring setup:
- Enable error notifications in your automation platform
- Set up a daily check (5 minutes each morning to review yesterday's runs)
- Create a simple spreadsheet to track automation health
- Set calendar reminders for weekly automation reviews
Real-world example: A consulting firm set up email notifications for automation failures. They received an alert within 5 minutes when their lead sync automation broke. They fixed it before any leads were lost. Without monitoring, they would have discovered the issue days later.
Pro Tip: Spend 10 minutes each Monday morning reviewing your automations. Check execution logs, verify outputs, and test connections. This weekly habit catches 90% of issues before they become problems.
When to Ask for Help vs. Fix It Yourself
You don't need to fix every automation issue yourself. Sometimes asking for help saves time and prevents bigger problems.
Fix it yourself when:
- The issue matches one of the five common problems (expired keys, rate limits, etc.)
- You can identify the failing step and understand the error message
- The fix takes less than 30 minutes
- You've successfully fixed similar issues before
Ask for help when:
- You've spent 2+ hours debugging without progress
- Multiple steps are failing and you can't identify the root cause
- The error message is unclear or points to a complex technical issue
- You're not confident the fix won't break something else
- The automation is business-critical and downtime costs money
Where to get help:
- Platform support: Most automation platforms offer support forums, documentation, and help centers
- Community forums: Reddit (r/automation, r/Make, r/n8n), platform-specific communities
- Professional help: Automation consultants or agencies (like Evalics) for complex issues
- Service providers: Contact the service you're automating (CRM, email platform, etc.) if the issue is on their end
Cost considerations:
- Self-fix: Free but costs your time (1-3 hours typically)
- Platform support: Usually free but may take 24-48 hours for response
- Community help: Free but quality varies
- Professional help: $100-300/hour but fixes issues quickly and prevents future problems
Key Insight: The cost of professional help is often less than the opportunity cost of spending hours debugging. If your automation handles $1,000+ in business value daily, a $200 fix that takes 1 hour is worth it compared to 8 hours of your time.
Conclusion
Debugging automation doesn't require technical expertise. It requires a systematic approach. Start by checking execution logs, verifying connections, and testing each step individually. Most failures come from five common issues: expired API keys, rate limits, changed interfaces, missing permissions, and data format changes.
Learn to read error messages, and you'll diagnose 90% of problems quickly. Set up simple monitoring to catch issues early. Know when to restart versus rebuild, and when to ask for help versus fixing it yourself.
The difference between business owners who succeed with automation and those who give up isn't technical skill. It's knowing how to troubleshoot methodically. Follow this process, and you'll fix most automation issues in under 30 minutes.
Ready to build automations that don't break? Book a demo with Evalics to learn how we help small businesses build reliable, maintainable automations that scale with their growth.
Frequently Asked Questions
How do I know if my automation is broken?
Look for these signs: no notifications or outputs, missing data in expected locations, error messages in your platform, automation runs but produces incorrect results, or automation doesn't trigger at all. Most platforms show red error indicators when something fails.
How long should I spend debugging before asking for help?
If you've spent 2+ hours debugging without progress, it's time to ask for help. Also ask for help if multiple steps are failing, error messages are unclear, or the automation is business-critical and downtime costs money.
What's the most common automation failure?
Expired API keys or OAuth tokens cause the most failures. Most tokens expire after 30-90 days. Set calendar reminders to check connections every 60 days to prevent this issue.
Can I prevent automation failures?
You can't prevent all failures, but you can reduce them significantly. Set up monitoring to catch issues early, check connections every 60 days, subscribe to service update notifications, and test automations with real data before going live.
How do I set up monitoring for my automations?
Enable error notifications in your automation platform. Most platforms (Make.com, n8n, Zapier) offer email or Slack alerts for failed executions. Spend 10 minutes each Monday reviewing your automations to catch issues early.
When should I rebuild an automation instead of fixing it?
Rebuild when multiple steps are failing, the service had a major update, your business process changed, or fixing takes more than 2-3 hours. If only 1-2 steps fail and the fix is straightforward, restarting is usually faster.
What if I can't understand the error message?
Start by identifying the error type (authentication, rate limit, data format, etc.). Most errors fall into five categories. If the message is still unclear, check platform documentation, search community forums, or ask for help. Don't spend hours guessing.
By Kevin Michael Schindler, AI Automation Expert at Evalics