Two n8n issues that look harmless but silently break your workflows:

1. The HTTP Request node shows a green ✅ but returns empty output
2. Your workflow times out before finishing — and you're not sure where to change the limit

Both are quick fixes once you know where to look.

Why "Check URL" Returns Success With No Data

n8n marks an HTTP Request as successful based on the HTTP status code only. A 200 OK = green tick — even if the response body is completely empty or contains an error message like {"error": "not found"}.

The fix is a Code node placed immediately after the HTTP Request:

const response = $input.item.json;

// Empty body check
if (!response || Object.keys(response).length === 0) {
  throw new Error('HTTP 200 OK but body is empty.');
}

// Missing data field check
if (!response.data || (Array.isArray(response.data) && response.data.length === 0)) {
  throw new Error('API returned no data. Raw: ' + JSON.stringify(response).substring(0, 200));
}

// Error hidden inside a 200 response
if (response.error || response.success === false) {
  throw new Error('API error in 200 body: ' + JSON.stringify(response.error));
}

return { json: response };

Now your workflow fails loudly with a clear message instead of passing empty data to every node downstream.

How to Configure Execution Timeout in Workflow Settings

The default execution timeout is 30 seconds. For workflows that call slow APIs, loop through many items, or process files, this is too short.

To change it:

1. Open your workflow in the n8n editor
2. Click the Settings gear icon (top-right, next to the workflow name)
3. Find Execution Timeout (seconds) — default: 30
4. Set it to 120 or 300 depending on your workflow
5. Click Save, then toggle the workflow off → on

Self-hosted n8n: add EXECUTIONS_TIMEOUT=120 to your .env file and restart.

Export the Workflow JSON (With Settings Included)

After saving, export via ⋮ menu → Export. Your JSON will include the timeout setting:

{
  "settings": {
    "executionOrder": "v1",
    "executionTimeout": 120
  }
}

If executionTimeout is missing from your exported file — you exported before saving. Always save first.

Still Timing Out After 300s?

Usually one of three causes:

• Infinite loop — Split In Batches connected back incorrectly
• Too many items — use smaller batch sizes (10–50 per batch)
• Slow API — add a Wait node between calls

For the full guide with more edge cases, code samples, and FAQ:
👉 n8n Check URL Node: Fix Success Error & Execution Timeout — TriggerWorkflow

I write practical n8n tutorials focused on real errors and production workflows. If you're building automation with n8n, you might also find these useful:

• Fix Webhook 404 "Not Registered" Error
• Fix Webhook URL Showing Localhost on VPS
• Complete Workflow Execution Failed Troubleshooting