ERR_ACTION_FAILED on Make.com: Action execution failed. Root cause: The target service received the API request but rejected it due to validation errors, missing required fields, permission restrictions, or a temporary service-side failure. The error payload from the target service typically contains the specific rejection reason. Step 1: Read the full error message from the failed module run. In Make.com, go to Activity → Scenario Runs and click the failed run. The timeline shows each module as a bubble — the failed module is highlighted in red. Click the red bubble to expand the error details. Make.com displays the full HTTP response from the target service, including the status code, error message, and often a specific field or validation error. Copy this error message before doing anything else — it contains the exact reason the action was rejected and will tell you which of the following steps to take. Step 2: Check whether the connected account still has the required permissions. Many action failures are caused by permission changes in the target app — an admin revoked API access, the connected user's role was downgraded, or the OAuth scope granted to Make.com no longer covers the action being attempted. Go to Make.com → Connections (left sidebar) → find the connection for the failing module → click the three-dot menu → "Verify". If verification fails, click "Reauthorise" and complete the OAuth flow. When reauthorising, ensure you are logged into the target app as the correct user with the necessary permissions. Step 3: Validate all required fields in the module configuration. Click the failing module to open its configuration. Look for any fields marked with a red asterisk (*) — these are required. Check whether any required field is mapped to a source value that could be empty. For example, if a "Create Contact" module requires an email address but the source record sometimes has no email, the module will fail for those records. Add a Filter before the module: "Only continue if [email field] exists" — this prevents the module from running when required data is missing. Step 4: Check for data format issues in the fields being sent. Even when all required fields are populated, the target service may reject the data if it is in the wrong format. Common issues: phone numbers sent without country code when the API requires +1-xxx-xxx-xxxx format; dates sent as "June 20, 2026" when the API expects "2026-06-20"; currency amounts sent as "$1,234.56" when the API expects "1234.56" (no currency symbol, no comma). Use Make.com's built-in functions to format the data before it reaches the module: formatDate() for dates, parseNumber() for currency amounts, and replace() to strip unwanted characters from phone numbers. Step 5: Add a Retry directive to handle temporary service failures. Some action failures are caused by temporary issues in the target service — a brief API outage, a database lock, or a rate limit. These will succeed if retried a few minutes later. Right-click the failing module → "Add error handler" → select "Retry". Configure the retry to attempt 3 times with a 5-minute interval. Make.com will automatically retry the failed bundle without creating duplicate records (most APIs are idempotent for create operations when given the same unique identifier). Check the run history after 15 minutes to confirm the retry succeeded. Step 6: Use the "Break" directive to isolate failing bundles without stopping the scenario. If your scenario processes multiple bundles (records) and one bundle causes an action failure, the default behaviour is to stop the entire scenario. To allow other bundles to continue processing, right-click the failing module → "Add error handler" → select "Break". Make.com will mark the failing bundle as incomplete and continue processing the remaining bundles. The incomplete bundles are stored in Activity → Incomplete Executions, where you can manually review and resume them once the underlying issue is fixed.