Why does my n8n workflow stop processing after a few links?

Below is some guidance to help troubleshoot this issue:

No Hard Execution Time Limit

n8n does not impose an arbitrary limit that stops workflows after processing 14–15 items. The message “execution completed” simply indicates that the workflow ran to completion with the items it received.

What to Check

• Input Data:
  Verify that the node feeding into your meta description extractor is indeed providing all the expected links. Sometimes a node (for example, one that retrieves URLs) may only yield a subset due to filtering or pagination.

• Node Connections and Configuration:
  Check that every node is correctly connected so that items flow through the entire workflow. If a node (or its connection) is configured to take only a single item or a limited set, later items might never be processed.

• Batch Processing:
  If you’re using a “Loop Over Items” or similar batching node, make sure its batch size and settings cover all your links. You might need to adjust the batch size to ensure all items are processed over multiple iterations.

• Workflow Mode:
  If you’re running the workflow in “Test” mode from the editor, note that in some cases the workflow might process just a subset of items for testing purposes. Running in production mode might process the full set.

Next Steps

1. Inspect the Trigger/Input:
   Confirm that the upstream node returns the complete list of links. You can add a Sticky Note node or a logging step to verify the number and content of items before passing them on.

2. Review Node Settings:
   Look over the configuration of each node (especially any looping or splitting node) to ensure there’s no accidental limit or filter applied.

3. Test with a Small Set:
   Run a test with a known complete set of links to see how many items are passed from one node to the next. This way you can pinpoint where the truncation happens.

There isn’t a default time or item limit that would explain the behavior you’re seeing. It’s most likely related to how the data is flowing (or not flowing) between the nodes. Reviewing each node’s settings and the connections between them should help resolve the issue.