@n8n-as-code/skills 1.2.0-next.16 → 1.2.0

package/dist/assets/n8n-docs-complete.json

@@ -1,8 +1,8 @@
 {
-  "generatedAt": "2026-03-24T17:41:39.576Z",
+  "generatedAt": "2026-03-25T07:18:21.020Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
-  "totalPages": 1253,
+  "totalPages": 1254,
   "statistics": {
     "byCategory": {
       "other": 515,
@@ -12,7 +12,7 @@
       "code": 20,
       "data": 38,
       "flow-logic": 8,
-      "hosting": 77,
+      "hosting": 78,
       "integrations": 305,
       "cluster-nodes": 98,
       "trigger-nodes": 107,
@@ -708,7 +708,7 @@
     },
     "hosting": {
       "description": "Self-hosting, deployment, and infrastructure",
-      "totalPages": 77,
+      "totalPages": 78,
       "pages": [
         "page-0150",
         "page-0151",
@@ -774,6 +774,7 @@
         "page-0211",
         "page-0212",
         "page-0213",
+        "page-0214",
         "page-0215",
         "page-0216",
         "page-0217",
@@ -4705,6 +4706,58 @@
     },
     {
       "id": "page-0035",
+      "title": "What is memory?",
+      "url": "https://docs.n8n.io/advanced-ai/examples/understand-memory/index.md",
+      "urlPath": "advanced-ai/examples/understand-memory/index.md",
+      "category": "advanced-ai",
+      "subcategory": "examples",
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# What's memory in AI?\n\nMemory is a key part of AI chat services. The [memory](../../../glossary/#ai-memory) keeps a history of previous messages, allowing for an ongoing conversation with the AI, rather than every interaction starting fresh.\n\n## AI memory in n8n\n\nTo add memory to your AI workflow you can use either:\n\n- [Simple Memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorybufferwindow/): stores a customizable length of chat history for the current session. This is the easiest to get started with.\n- One of the memory services that n8n provides nodes for. These include:\n  - [Motorhead](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorymotorhead/)\n  - [Redis Chat Memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryredischat/)\n  - [Postgres Chat Memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorypostgreschat/)\n  - [Xata](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryxata/)\n  - [Zep](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryzep/)\n\nIf you need to do advanced AI memory management in your workflows, use the [Chat Memory Manager](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorymanager/) node.\n\nThis node is useful when you:\n\n- Can't add a memory node directly.\n- Need to do more complex memory management, beyond what the memory nodes offer. For example, you can add this node to check the memory size of the Agent node's response, and reduce it if needed.\n- Want to inject messages to the AI that look like user messages, to give the AI more context.\n",
+        "excerpt": "# What's memory in AI?  Memory is a key part of AI chat services. The [memory](../../../glossary/#ai-memory) keeps a history of previous messages, allowing for an ongoing conversation with the AI, rather than every interaction starting fresh.  ## AI memory in n8n  To add memory to your AI workflow you can use either:  - [Simple Memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorybufferwindow/): stores a customizable length of chat history for the current sessi...",
+        "sections": [
+          {
+            "title": "What's memory in AI?",
+            "level": 1,
+            "content": "Memory is a key part of AI chat services. The [memory](../../../glossary/#ai-memory) keeps a history of previous messages, allowing for an ongoing conversation with the AI, rather than every interaction starting fresh."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "what",
+          "memory?",
+          "what's",
+          "memory"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 1711,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "what is memory? # what's memory in ai?\n\nmemory is a key part of ai chat services. the [memory](../../../glossary/#ai-memory) keeps a history of previous messages, allowing for an ongoing conversation with the ai, rather than every interaction starting fresh.\n\n## ai memory in n8n\n\nto add memory to your ai workflow you can use either:\n\n- [simple memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorybufferwindow/): stores a customizable length of chat history for the current session. this is the easiest to get started with.\n- one of the memory services that n8n provides nodes for. these include:\n  - [motorhead](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorymotorhead/)\n  - [redis chat memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryredischat/)\n  - [postgres chat memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorypostgreschat/)\n  - [xata](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryxata/)\n  - [zep](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryzep/)\n\nif you need to do advanced ai memory management in your workflows, use the [chat memory manager](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorymanager/) node.\n\nthis node is useful when you:\n\n- can't add a memory node directly.\n- need to do more complex memory management, beyond what the memory nodes offer. for example, you can add this node to check the memory size of the agent node's response, and reduce it if needed.\n- want to inject messages to the ai that look like user messages, to give the ai more context.\n what's memory in ai?",
+        "importantTerms": [
+          "nodes",
+          "memory",
+          "integrations",
+          "builtin",
+          "cluster",
+          "langchain",
+          "chat",
+          "node",
+          "what",
+          "messages",
+          "this"
+        ]
+      }
+    },
+    {
+      "id": "page-0036",
       "title": "What is a tool?",
       "url": "https://docs.n8n.io/advanced-ai/examples/understand-tools/index.md",
       "urlPath": "advanced-ai/examples/understand-tools/index.md",
@@ -4761,7 +4814,7 @@
       }
     },
     {
-      "id": "page-0036",
+      "id": "page-0037",
       "title": "What is a vector database?",
       "url": "https://docs.n8n.io/advanced-ai/examples/understand-vector-databases/index.md",
       "urlPath": "advanced-ai/examples/understand-vector-databases/index.md",
@@ -4853,7 +4906,7 @@
       }
     },
     {
-      "id": "page-0037",
+      "id": "page-0038",
       "title": "Let AI specify tool parameters",
       "url": "https://docs.n8n.io/advanced-ai/examples/using-the-fromai-function/index.md",
       "urlPath": "advanced-ai/examples/using-the-fromai-function/index.md",
@@ -4946,7 +4999,7 @@
       }
     },
     {
-      "id": "page-0038",
+      "id": "page-0039",
       "title": "Populate a Pinecone vector database from a website",
       "url": "https://docs.n8n.io/advanced-ai/examples/vector-store-website/index.md",
       "urlPath": "advanced-ai/examples/vector-store-website/index.md",
@@ -5016,58 +5069,6 @@
         ]
       }
     },
-    {
-      "id": "page-0039",
-      "title": "What is memory?",
-      "url": "https://docs.n8n.io/advanced-ai/examples/understand-memory/index.md",
-      "urlPath": "advanced-ai/examples/understand-memory/index.md",
-      "category": "advanced-ai",
-      "subcategory": "examples",
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# What's memory in AI?\n\nMemory is a key part of AI chat services. The [memory](../../../glossary/#ai-memory) keeps a history of previous messages, allowing for an ongoing conversation with the AI, rather than every interaction starting fresh.\n\n## AI memory in n8n\n\nTo add memory to your AI workflow you can use either:\n\n- [Simple Memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorybufferwindow/): stores a customizable length of chat history for the current session. This is the easiest to get started with.\n- One of the memory services that n8n provides nodes for. These include:\n  - [Motorhead](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorymotorhead/)\n  - [Redis Chat Memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryredischat/)\n  - [Postgres Chat Memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorypostgreschat/)\n  - [Xata](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryxata/)\n  - [Zep](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryzep/)\n\nIf you need to do advanced AI memory management in your workflows, use the [Chat Memory Manager](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorymanager/) node.\n\nThis node is useful when you:\n\n- Can't add a memory node directly.\n- Need to do more complex memory management, beyond what the memory nodes offer. For example, you can add this node to check the memory size of the Agent node's response, and reduce it if needed.\n- Want to inject messages to the AI that look like user messages, to give the AI more context.\n",
-        "excerpt": "# What's memory in AI?  Memory is a key part of AI chat services. The [memory](../../../glossary/#ai-memory) keeps a history of previous messages, allowing for an ongoing conversation with the AI, rather than every interaction starting fresh.  ## AI memory in n8n  To add memory to your AI workflow you can use either:  - [Simple Memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorybufferwindow/): stores a customizable length of chat history for the current sessi...",
-        "sections": [
-          {
-            "title": "What's memory in AI?",
-            "level": 1,
-            "content": "Memory is a key part of AI chat services. The [memory](../../../glossary/#ai-memory) keeps a history of previous messages, allowing for an ongoing conversation with the AI, rather than every interaction starting fresh."
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "what",
-          "memory?",
-          "what's",
-          "memory"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "1 min",
-        "contentLength": 1711,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "what is memory? # what's memory in ai?\n\nmemory is a key part of ai chat services. the [memory](../../../glossary/#ai-memory) keeps a history of previous messages, allowing for an ongoing conversation with the ai, rather than every interaction starting fresh.\n\n## ai memory in n8n\n\nto add memory to your ai workflow you can use either:\n\n- [simple memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorybufferwindow/): stores a customizable length of chat history for the current session. this is the easiest to get started with.\n- one of the memory services that n8n provides nodes for. these include:\n  - [motorhead](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorymotorhead/)\n  - [redis chat memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryredischat/)\n  - [postgres chat memory](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorypostgreschat/)\n  - [xata](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryxata/)\n  - [zep](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memoryzep/)\n\nif you need to do advanced ai memory management in your workflows, use the [chat memory manager](../../../integrations/builtin/cluster-nodes/sub-nodes/n8n-nodes-langchain.memorymanager/) node.\n\nthis node is useful when you:\n\n- can't add a memory node directly.\n- need to do more complex memory management, beyond what the memory nodes offer. for example, you can add this node to check the memory size of the agent node's response, and reduce it if needed.\n- want to inject messages to the ai that look like user messages, to give the ai more context.\n what's memory in ai?",
-        "importantTerms": [
-          "nodes",
-          "memory",
-          "integrations",
-          "builtin",
-          "cluster",
-          "langchain",
-          "chat",
-          "node",
-          "what",
-          "messages",
-          "this"
-        ]
-      }
-    },
     {
       "id": "page-0040",
       "title": "LangChain learning resources",
@@ -18107,28 +18108,38 @@
     },
     {
       "id": "page-0213",
-      "title": "Overview",
-      "url": "https://docs.n8n.io/hosting/scaling/overview/index.md",
-      "urlPath": "hosting/scaling/overview/index.md",
+      "title": "Memory-related errors",
+      "url": "https://docs.n8n.io/hosting/scaling/memory-errors/index.md",
+      "urlPath": "hosting/scaling/memory-errors/index.md",
       "category": "hosting",
       "subcategory": null,
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Scaling n8n\n\nWhen running n8n at scale, with a large number of users, workflows, or executions, you need to change your n8n configuration to ensure good performance.\n\nn8n can run in different [modes](../queue-mode/) depending on your needs. The `queue` mode provides the best scalability. Refer to [Queue mode](../queue-mode/) for configuration details.\n\nYou can configure data saving and pruning to improve database performance. Refer to [Execution data](../execution-data/) for details.\n](../../../manage-cloud/overview/).\n\n## Identifying out of memory situations\n\nn8n provides error messages that warn you in some out of memory situations. For example, messages such as **Execution stopped at this node (n8n may have run out of memory while executing it)**.\n\nError messages including **Problem running workflow**, **Connection Lost**, or **503 Service Temporarily Unavailable** suggest that an n8n instance has become unavailable.\n\nWhen self-hosting n8n, you may also see error messages such as **Allocation failed - JavaScript heap out of memory** in your server logs.\n\nOn n8n Cloud, or when using n8n's Docker image, n8n restarts automatically when encountering such an issue. However, when running n8n with npm you might need to restart it manually.\n\n## Typical causes\n\nSuch problems occur when a workflow execution requires more memory than available to an n8n instance. Factors increasing the memory usage for a workflow execution include:\n\n- Amount of [JSON data](../../../data/data-structure/).\n- Size of binary data.\n- Number of nodes in a workflow.\n- Some nodes are memory-heavy: the [Code](../../../integrations/builtin/core-nodes/n8n-nodes-base.code/) node and the older Function node can increase memory consumption significantly.\n- Manual or automatic workflow executions: manual executions increase memory consumption as n8n makes a copy of the data for the frontend.\n- Additional workflows running at the same time.\n\n## Avoiding out of memory situations\n\nWhen encountering an out of memory situation, there are two options: either increase the amount of memory available to n8n or reduce the memory consumption.\n\n### Increase available memory\n\nWhen self-hosting n8n, increasing the amount of memory available to n8n means provisioning your n8n instance with more memory. This may incur additional costs with your hosting provider.\n\nOn n8n cloud you need to upgrade to a larger plan.\n\n### Reduce memory consumption\n\nThis approach is more complex and means re-building the workflows causing the issue. This section provides some guidelines on how to reduce memory consumption. Not all suggestions are applicable to all workflows.\n\n- Split the data processed into smaller chunks. For example, instead of fetching 10,000 rows with each execution, process 200 rows with each execution.\n- Avoid using the Code node where possible.\n- Avoid manual executions when processing larger amounts of data.\n- Split the workflow up into sub-workflows and ensure each sub-workflow returns a limited amount of data to its parent workflow.\n\nSplitting the workflow might seem counter-intuitive at first as it usually requires adding at least two more nodes: the [Loop Over Items](../../../integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/) node to split up the items into smaller batches and the [Execute Workflow](../../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) node to start the sub-workflow.\n\nHowever, as long as your sub-workflow does the heavy lifting for each batch and then returns only a small result set to the main workflow, this reduces memory consumption. This is because the sub-workflow only holds the data for the current batch in memory, after which the memory is free again.\n\n### Increase old memory\n\nThis applies to self-hosting n8n. When encountering **JavaScript heap out of memory** errors, it's often useful to allocate additional memory to the old memory section of the V8 JavaScript engine. To do this, set the appropriate [V8 option](https://nodejs.org/api/cli.html#--max-old-space-sizesize-in-megabytes) `--max-old-space-size=SIZE` either through the CLI or through the `NODE_OPTIONS` [environment variable](https://nodejs.org/api/cli.html#node_optionsoptions).\n",
-        "excerpt": "# Scaling n8n  When running n8n at scale, with a large number of users, workflows, or executions, you need to change your n8n configuration to ensure good performance.  n8n can run in different [modes](../queue-mode/) depending on your needs. The `queue` mode provides the best scalability. Refer to [Queue mode](../queue-mode/) for configuration details.  You can configure data saving and pruning to improve database performance. Refer to [Execution data](../execution-data/) for details. ](../../....",
+        "markdown": "# Memory-related errors\n\nn8n doesn't restrict the amount of data each node can fetch and process. While this gives you freedom, it can lead to errors when workflow executions require more memory than available. This page explains how to identify and avoid these errors.\n\nOnly for self-hosted n8n\n\nThis page describes memory-related errors when [self-hosting n8n](../../). Visit [Cloud data management](../../../manage-cloud/cloud-data-management/) to learn about memory limits for [n8n Cloud](../../../manage-cloud/overview/).\n\n## Identifying out of memory situations\n\nn8n provides error messages that warn you in some out of memory situations. For example, messages such as **Execution stopped at this node (n8n may have run out of memory while executing it)**.\n\nError messages including **Problem running workflow**, **Connection Lost**, or **503 Service Temporarily Unavailable** suggest that an n8n instance has become unavailable.\n\nWhen self-hosting n8n, you may also see error messages such as **Allocation failed - JavaScript heap out of memory** in your server logs.\n\nOn n8n Cloud, or when using n8n's Docker image, n8n restarts automatically when encountering such an issue. However, when running n8n with npm you might need to restart it manually.\n\n## Typical causes\n\nSuch problems occur when a workflow execution requires more memory than available to an n8n instance. Factors increasing the memory usage for a workflow execution include:\n\n- Amount of [JSON data](../../../data/data-structure/).\n- Size of binary data.\n- Number of nodes in a workflow.\n- Some nodes are memory-heavy: the [Code](../../../integrations/builtin/core-nodes/n8n-nodes-base.code/) node and the older Function node can increase memory consumption significantly.\n- Manual or automatic workflow executions: manual executions increase memory consumption as n8n makes a copy of the data for the frontend.\n- Additional workflows running at the same time.\n\n## Avoiding out of memory situations\n\nWhen encountering an out of memory situation, there are two options: either increase the amount of memory available to n8n or reduce the memory consumption.\n\n### Increase available memory\n\nWhen self-hosting n8n, increasing the amount of memory available to n8n means provisioning your n8n instance with more memory. This may incur additional costs with your hosting provider.\n\nOn n8n cloud you need to upgrade to a larger plan.\n\n### Reduce memory consumption\n\nThis approach is more complex and means re-building the workflows causing the issue. This section provides some guidelines on how to reduce memory consumption. Not all suggestions are applicable to all workflows.\n\n- Split the data processed into smaller chunks. For example, instead of fetching 10,000 rows with each execution, process 200 rows with each execution.\n- Avoid using the Code node where possible.\n- Avoid manual executions when processing larger amounts of data.\n- Split the workflow up into sub-workflows and ensure each sub-workflow returns a limited amount of data to its parent workflow.\n\nSplitting the workflow might seem counter-intuitive at first as it usually requires adding at least two more nodes: the [Loop Over Items](../../../integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/) node to split up the items into smaller batches and the [Execute Workflow](../../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) node to start the sub-workflow.\n\nHowever, as long as your sub-workflow does the heavy lifting for each batch and then returns only a small result set to the main workflow, this reduces memory consumption. This is because the sub-workflow only holds the data for the current batch in memory, after which the memory is free again.\n\n### Increase old memory\n\nThis applies to self-hosting n8n. When encountering **JavaScript heap out of memory** errors, it's often useful to allocate additional memory to the old memory section of the V8 JavaScript engine. To do this, set the appropriate [V8 option](https://nodejs.org/api/cli.html#--max-old-space-sizesize-in-megabytes) `--max-old-space-size=SIZE` either through the CLI or through the `NODE_OPTIONS` [environment variable](https://nodejs.org/api/cli.html#node_optionsoptions).\n",
+        "excerpt": "# Memory-related errors  n8n doesn't restrict the amount of data each node can fetch and process. While this gives you freedom, it can lead to errors when workflow executions require more memory than available. This page explains how to identify and avoid these errors.  Only for self-hosted n8n  This page describes memory-related errors when [self-hosting n8n](../../). Visit [Cloud data management](../../../manage-cloud/cloud-data-management/) to learn about memory limits for [n8n Cloud](../../....",
         "sections": [
           {
-            "title": "Scaling n8n",
+            "title": "Memory-related errors",
             "level": 1,
-            "content": "When running n8n at scale, with a large number of users, workflows, or executions, you need to change your n8n configuration to ensure good performance.\n\nn8n can run in different [modes](../queue-mode/) depending on your needs. The `queue` mode provides the best scalability. Refer to [Queue mode](../queue-mode/) for configuration details.\n\nYou can configure data saving and pruning to improve database performance. Refer to [Execution data](../execution-data/) for details.\n](../../../manage-cloud/overview/)."
+            "content": "n8n doesn't restrict the amount of data each node can fetch and process. While this gives you freedom, it can lead to errors when workflow executions require more memory than available. This page explains how to identify and avoid these errors.\n\nOnly for self-hosted n8n\n\nThis page describes memory-related errors when [self-hosting n8n](../../). Visit [Cloud data management](../../../manage-cloud/cloud-data-management/) to learn about memory limits for [n8n Cloud](../../../manage-cloud/overview/)."
           }
         ]
       },
       "metadata": {
         "keywords": [
-          "overview",
-          "scaling"
+          "memory",
+          "related",
+          "errors",
+          "identifying",
+          "situations",
+          "typical",
+          "causes",
+          "avoiding",
+          "increase",
+          "available",
+          "reduce",
+          "consumption"
         ],
         "useCases": [],
         "operations": [],
@@ -18139,40 +18150,40 @@
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "overview # scaling n8n\n\nwhen running n8n at scale, with a large number of users, workflows, or executions, you need to change your n8n configuration to ensure good performance.\n\nn8n can run in different [modes](../queue-mode/) depending on your needs. the `queue` mode provides the best scalability. refer to [queue mode](../queue-mode/) for configuration details.\n\nyou can configure data saving and pruning to improve database performance. refer to [execution data](../execution-data/) for details.\n](../../../manage-cloud/overview/).\n\n## identifying out of memory situations\n\nn8n provides error messages that warn you in some out of memory situations. for example, messages such as **execution stopped at this node (n8n may have run out of memory while executing it)**.\n\nerror messages including **problem running workflow**, **connection lost**, or **503 service temporarily unavailable** suggest that an n8n instance has become unavailable.\n\nwhen self-hosting n8n, you may also see error messages such as **allocation failed - javascript heap out of memory** in your server logs.\n\non n8n cloud, or when using n8n's docker image, n8n restarts automatically when encountering such an issue. however, when running n8n with npm you might need to restart it manually.\n\n## typical causes\n\nsuch problems occur when a workflow execution requires more memory than available to an n8n instance. factors increasing the memory usage for a workflow execution include:\n\n- amount of [json data](../../../data/data-structure/).\n- size of binary data.\n- number of nodes in a workflow.\n- some nodes are memory-heavy: the [code](../../../integrations/builtin/core-nodes/n8n-nodes-base.code/) node and the older function node can increase memory consumption significantly.\n- manual or automatic workflow executions: manual executions increase memory consumption as n8n makes a copy of the data for the frontend.\n- additional workflows running at the same time.\n\n## avoiding out of memory situations\n\nwhen encountering an out of memory situation, there are two options: either increase the amount of memory available to n8n or reduce the memory consumption.\n\n### increase available memory\n\nwhen self-hosting n8n, increasing the amount of memory available to n8n means provisioning your n8n instance with more memory. this may incur additional costs with your hosting provider.\n\non n8n cloud you need to upgrade to a larger plan.\n\n### reduce memory consumption\n\nthis approach is more complex and means re-building the workflows causing the issue. this section provides some guidelines on how to reduce memory consumption. not all suggestions are applicable to all workflows.\n\n- split the data processed into smaller chunks. for example, instead of fetching 10,000 rows with each execution, process 200 rows with each execution.\n- avoid using the code node where possible.\n- avoid manual executions when processing larger amounts of data.\n- split the workflow up into sub-workflows and ensure each sub-workflow returns a limited amount of data to its parent workflow.\n\nsplitting the workflow might seem counter-intuitive at first as it usually requires adding at least two more nodes: the [loop over items](../../../integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/) node to split up the items into smaller batches and the [execute workflow](../../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) node to start the sub-workflow.\n\nhowever, as long as your sub-workflow does the heavy lifting for each batch and then returns only a small result set to the main workflow, this reduces memory consumption. this is because the sub-workflow only holds the data for the current batch in memory, after which the memory is free again.\n\n### increase old memory\n\nthis applies to self-hosting n8n. when encountering **javascript heap out of memory** errors, it's often useful to allocate additional memory to the old memory section of the v8 javascript engine. to do this, set the appropriate [v8 option](https://nodejs.org/api/cli.html#--max-old-space-sizesize-in-megabytes) `--max-old-space-size=size` either through the cli or through the `node_options` [environment variable](https://nodejs.org/api/cli.html#node_optionsoptions).\n scaling n8n",
+        "fullText": "memory-related errors # memory-related errors\n\nn8n doesn't restrict the amount of data each node can fetch and process. while this gives you freedom, it can lead to errors when workflow executions require more memory than available. this page explains how to identify and avoid these errors.\n\nonly for self-hosted n8n\n\nthis page describes memory-related errors when [self-hosting n8n](../../). visit [cloud data management](../../../manage-cloud/cloud-data-management/) to learn about memory limits for [n8n cloud](../../../manage-cloud/overview/).\n\n## identifying out of memory situations\n\nn8n provides error messages that warn you in some out of memory situations. for example, messages such as **execution stopped at this node (n8n may have run out of memory while executing it)**.\n\nerror messages including **problem running workflow**, **connection lost**, or **503 service temporarily unavailable** suggest that an n8n instance has become unavailable.\n\nwhen self-hosting n8n, you may also see error messages such as **allocation failed - javascript heap out of memory** in your server logs.\n\non n8n cloud, or when using n8n's docker image, n8n restarts automatically when encountering such an issue. however, when running n8n with npm you might need to restart it manually.\n\n## typical causes\n\nsuch problems occur when a workflow execution requires more memory than available to an n8n instance. factors increasing the memory usage for a workflow execution include:\n\n- amount of [json data](../../../data/data-structure/).\n- size of binary data.\n- number of nodes in a workflow.\n- some nodes are memory-heavy: the [code](../../../integrations/builtin/core-nodes/n8n-nodes-base.code/) node and the older function node can increase memory consumption significantly.\n- manual or automatic workflow executions: manual executions increase memory consumption as n8n makes a copy of the data for the frontend.\n- additional workflows running at the same time.\n\n## avoiding out of memory situations\n\nwhen encountering an out of memory situation, there are two options: either increase the amount of memory available to n8n or reduce the memory consumption.\n\n### increase available memory\n\nwhen self-hosting n8n, increasing the amount of memory available to n8n means provisioning your n8n instance with more memory. this may incur additional costs with your hosting provider.\n\non n8n cloud you need to upgrade to a larger plan.\n\n### reduce memory consumption\n\nthis approach is more complex and means re-building the workflows causing the issue. this section provides some guidelines on how to reduce memory consumption. not all suggestions are applicable to all workflows.\n\n- split the data processed into smaller chunks. for example, instead of fetching 10,000 rows with each execution, process 200 rows with each execution.\n- avoid using the code node where possible.\n- avoid manual executions when processing larger amounts of data.\n- split the workflow up into sub-workflows and ensure each sub-workflow returns a limited amount of data to its parent workflow.\n\nsplitting the workflow might seem counter-intuitive at first as it usually requires adding at least two more nodes: the [loop over items](../../../integrations/builtin/core-nodes/n8n-nodes-base.splitinbatches/) node to split up the items into smaller batches and the [execute workflow](../../../integrations/builtin/core-nodes/n8n-nodes-base.executeworkflow/) node to start the sub-workflow.\n\nhowever, as long as your sub-workflow does the heavy lifting for each batch and then returns only a small result set to the main workflow, this reduces memory consumption. this is because the sub-workflow only holds the data for the current batch in memory, after which the memory is free again.\n\n### increase old memory\n\nthis applies to self-hosting n8n. when encountering **javascript heap out of memory** errors, it's often useful to allocate additional memory to the old memory section of the v8 javascript engine. to do this, set the appropriate [v8 option](https://nodejs.org/api/cli.html#--max-old-space-sizesize-in-megabytes) `--max-old-space-size=size` either through the cli or through the `node_options` [environment variable](https://nodejs.org/api/cli.html#node_optionsoptions).\n memory-related errors",
         "importantTerms": [
           "memory",
           "workflow",
           "data",
+          "this",
           "when",
           "nodes",
-          "this",
-          "execution",
-          "with",
-          "your",
+          "errors",
           "node",
+          "cloud",
           "consumption",
-          "workflows",
+          "amount",
+          "each",
+          "more",
+          "available",
+          "self",
+          "hosting",
+          "execution",
+          "with",
           "increase",
-          "running",
+          "related",
           "executions",
-          "queue",
-          "mode",
           "messages",
           "such",
-          "hosting",
-          "more",
-          "available",
-          "amount",
-          "each",
-          "need",
-          "provides",
-          "cloud",
+          "your",
+          "workflows",
+          "avoid",
+          "only",
           "situations",
           "error",
           "some",
+          "running",
           "instance",
-          "self",
           "javascript",
           "encountering",
           "size",
@@ -18189,6 +18200,48 @@
         ]
       }
     },
+    {
+      "id": "page-0214",
+      "title": "Overview",
+      "url": "https://docs.n8n.io/hosting/scaling/overview/index.md",
+      "urlPath": "hosting/scaling/overview/index.md",
+      "category": "hosting",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Scaling n8n\n\nWhen running n8n at scale, with a large number of users, workflows, or executions, you need to change your n8n configuration to ensure good performance.\n\nn8n can run in different [modes](../queue-mode/) depending on your needs. The `queue` mode provides the best scalability. Refer to [Queue mode](../queue-mode/) for configuration details.\n\nYou can configure data saving and pruning to improve database performance. Refer to [Execution data](../execution-data/) for details.\n",
+        "excerpt": "# Scaling n8n  When running n8n at scale, with a large number of users, workflows, or executions, you need to change your n8n configuration to ensure good performance.  n8n can run in different [modes](../queue-mode/) depending on your needs. The `queue` mode provides the best scalability. Refer to [Queue mode](../queue-mode/) for configuration details.  You can configure data saving and pruning to improve database performance. Refer to [Execution data](../execution-data/) for details....",
+        "sections": [
+          {
+            "title": "Scaling n8n",
+            "level": 1,
+            "content": "When running n8n at scale, with a large number of users, workflows, or executions, you need to change your n8n configuration to ensure good performance.\n\nn8n can run in different [modes](../queue-mode/) depending on your needs. The `queue` mode provides the best scalability. Refer to [Queue mode](../queue-mode/) for configuration details.\n\nYou can configure data saving and pruning to improve database performance. Refer to [Execution data](../execution-data/) for details."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "overview",
+          "scaling"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "1 min",
+        "contentLength": 491,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "overview # scaling n8n\n\nwhen running n8n at scale, with a large number of users, workflows, or executions, you need to change your n8n configuration to ensure good performance.\n\nn8n can run in different [modes](../queue-mode/) depending on your needs. the `queue` mode provides the best scalability. refer to [queue mode](../queue-mode/) for configuration details.\n\nyou can configure data saving and pruning to improve database performance. refer to [execution data](../execution-data/) for details.\n scaling n8n",
+        "importantTerms": [
+          "queue",
+          "mode",
+          "data"
+        ]
+      }
+    },
     {
       "id": "page-0215",
       "title": "Performance and benchmarking",
@@ -73211,6 +73264,73 @@
     },
     {
       "id": "page-0979",
+      "title": "Twake credentials",
+      "url": "https://docs.n8n.io/integrations/builtin/credentials/twake/index.md",
+      "urlPath": "integrations/builtin/credentials/twake/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Twake credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Twake](../../app-nodes/n8n-nodes-base.twake/)\n\n## Prerequisites\n\nCreate a [Twake](https://twake.app/) account.\n\n## Supported authentication methods\n\n- Cloud API key\n- Server API key\n\n## Related resources\n\nRefer to [Twake's documentation](https://doc.twake.app/developers-api/api-reference) for more information about the service.\n\n## Using Cloud API key\n\nTo configure this credential, you'll need:\n\n- A **Workspace Key**: Generated when you install the **n8n** application to your Twake Cloud environment and select **Configure**. Refer to [How to connect n8n to Twake](https://help.twake.app/en/latest/applications/connectors/index.html#how-to-connect-n8n-to-twake) for more detailed instructions.\n\n## Using Server API key\n\nTo configure this credential, you'll need:\n\n- A **Host URL**: The URL of your Twake self-hosted instance.\n- A **Public ID**: Generated when you create an app.\n- A **Private API Key**: Generated when you create an app.\n\nTo generate your **Public ID** and **Private API Key**, [create a Twake application](https://doc.twake.app/developers-api/get-started/create-your-first-application):\n\n1. Go to **Workspace Settings > Applications and connectors > Access your applications and connectors > Create an application**.\n1. Enter appropriate details.\n1. Once you've created your app, view its **API Details**.\n1. Copy the **Public identifier** and add it as the n8n **Public ID**.\n1. Copy the **Private key** and add it as the n8n **Private API Key**.\n\nRefer to [API settings](https://doc.twake.app/developers-api/get-started/create-your-first-application#id-3.-api-settings) for more information.\n",
+        "excerpt": "# Twake credentials  You can use these credentials to authenticate the following nodes:  - [Twake](../../app-nodes/n8n-nodes-base.twake/)  ## Prerequisites  Create a [Twake](https://twake.app/) account.  ## Supported authentication methods  - Cloud API key - Server API key  ## Related resources  Refer to [Twake's documentation](https://doc.twake.app/developers-api/api-reference) for more information about the service.  ## Using Cloud API key  To configure this credential, you'll need:  - A **Wor...",
+        "sections": [
+          {
+            "title": "Twake credentials",
+            "level": 1,
+            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Twake](../../app-nodes/n8n-nodes-base.twake/)"
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "twake",
+          "credentials",
+          "prerequisites",
+          "supported",
+          "authentication",
+          "methods",
+          "related",
+          "resources",
+          "using",
+          "cloud",
+          "server"
+        ],
+        "useCases": [],
+        "operations": [],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "2 min",
+        "contentLength": 1709,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "twake credentials # twake credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [twake](../../app-nodes/n8n-nodes-base.twake/)\n\n## prerequisites\n\ncreate a [twake](https://twake.app/) account.\n\n## supported authentication methods\n\n- cloud api key\n- server api key\n\n## related resources\n\nrefer to [twake's documentation](https://doc.twake.app/developers-api/api-reference) for more information about the service.\n\n## using cloud api key\n\nto configure this credential, you'll need:\n\n- a **workspace key**: generated when you install the **n8n** application to your twake cloud environment and select **configure**. refer to [how to connect n8n to twake](https://help.twake.app/en/latest/applications/connectors/index.html#how-to-connect-n8n-to-twake) for more detailed instructions.\n\n## using server api key\n\nto configure this credential, you'll need:\n\n- a **host url**: the url of your twake self-hosted instance.\n- a **public id**: generated when you create an app.\n- a **private api key**: generated when you create an app.\n\nto generate your **public id** and **private api key**, [create a twake application](https://doc.twake.app/developers-api/get-started/create-your-first-application):\n\n1. go to **workspace settings > applications and connectors > access your applications and connectors > create an application**.\n1. enter appropriate details.\n1. once you've created your app, view its **api details**.\n1. copy the **public identifier** and add it as the n8n **public id**.\n1. copy the **private key** and add it as the n8n **private api key**.\n\nrefer to [api settings](https://doc.twake.app/developers-api/get-started/create-your-first-application#id-3.-api-settings) for more information.\n twake credentials",
+        "importantTerms": [
+          "twake",
+          "create",
+          "your",
+          "https",
+          "application",
+          "credentials",
+          "public",
+          "private",
+          "nodes",
+          "cloud",
+          "refer",
+          "developers",
+          "more",
+          "configure",
+          "generated",
+          "when",
+          "applications",
+          "connectors",
+          "settings"
+        ]
+      }
+    },
+    {
+      "id": "page-0980",
       "title": "Twilio credentials",
       "url": "https://docs.n8n.io/integrations/builtin/credentials/twilio/index.md",
       "urlPath": "integrations/builtin/credentials/twilio/index.md",
@@ -73290,73 +73410,6 @@
         ]
       }
     },
-    {
-      "id": "page-0980",
-      "title": "Twake credentials",
-      "url": "https://docs.n8n.io/integrations/builtin/credentials/twake/index.md",
-      "urlPath": "integrations/builtin/credentials/twake/index.md",
-      "category": "other",
-      "subcategory": null,
-      "nodeName": null,
-      "nodeType": null,
-      "content": {
-        "markdown": "# Twake credentials\n\nYou can use these credentials to authenticate the following nodes:\n\n- [Twake](../../app-nodes/n8n-nodes-base.twake/)\n\n## Prerequisites\n\nCreate a [Twake](https://twake.app/) account.\n\n## Supported authentication methods\n\n- Cloud API key\n- Server API key\n\n## Related resources\n\nRefer to [Twake's documentation](https://doc.twake.app/developers-api/api-reference) for more information about the service.\n\n## Using Cloud API key\n\nTo configure this credential, you'll need:\n\n- A **Workspace Key**: Generated when you install the **n8n** application to your Twake Cloud environment and select **Configure**. Refer to [How to connect n8n to Twake](https://help.twake.app/en/latest/applications/connectors/index.html#how-to-connect-n8n-to-twake) for more detailed instructions.\n\n## Using Server API key\n\nTo configure this credential, you'll need:\n\n- A **Host URL**: The URL of your Twake self-hosted instance.\n- A **Public ID**: Generated when you create an app.\n- A **Private API Key**: Generated when you create an app.\n\nTo generate your **Public ID** and **Private API Key**, [create a Twake application](https://doc.twake.app/developers-api/get-started/create-your-first-application):\n\n1. Go to **Workspace Settings > Applications and connectors > Access your applications and connectors > Create an application**.\n1. Enter appropriate details.\n1. Once you've created your app, view its **API Details**.\n1. Copy the **Public identifier** and add it as the n8n **Public ID**.\n1. Copy the **Private key** and add it as the n8n **Private API Key**.\n\nRefer to [API settings](https://doc.twake.app/developers-api/get-started/create-your-first-application#id-3.-api-settings) for more information.\n",
-        "excerpt": "# Twake credentials  You can use these credentials to authenticate the following nodes:  - [Twake](../../app-nodes/n8n-nodes-base.twake/)  ## Prerequisites  Create a [Twake](https://twake.app/) account.  ## Supported authentication methods  - Cloud API key - Server API key  ## Related resources  Refer to [Twake's documentation](https://doc.twake.app/developers-api/api-reference) for more information about the service.  ## Using Cloud API key  To configure this credential, you'll need:  - A **Wor...",
-        "sections": [
-          {
-            "title": "Twake credentials",
-            "level": 1,
-            "content": "You can use these credentials to authenticate the following nodes:\n\n- [Twake](../../app-nodes/n8n-nodes-base.twake/)"
-          }
-        ]
-      },
-      "metadata": {
-        "keywords": [
-          "twake",
-          "credentials",
-          "prerequisites",
-          "supported",
-          "authentication",
-          "methods",
-          "related",
-          "resources",
-          "using",
-          "cloud",
-          "server"
-        ],
-        "useCases": [],
-        "operations": [],
-        "codeExamples": 0,
-        "complexity": "beginner",
-        "readingTime": "2 min",
-        "contentLength": 1709,
-        "relatedPages": []
-      },
-      "searchIndex": {
-        "fullText": "twake credentials # twake credentials\n\nyou can use these credentials to authenticate the following nodes:\n\n- [twake](../../app-nodes/n8n-nodes-base.twake/)\n\n## prerequisites\n\ncreate a [twake](https://twake.app/) account.\n\n## supported authentication methods\n\n- cloud api key\n- server api key\n\n## related resources\n\nrefer to [twake's documentation](https://doc.twake.app/developers-api/api-reference) for more information about the service.\n\n## using cloud api key\n\nto configure this credential, you'll need:\n\n- a **workspace key**: generated when you install the **n8n** application to your twake cloud environment and select **configure**. refer to [how to connect n8n to twake](https://help.twake.app/en/latest/applications/connectors/index.html#how-to-connect-n8n-to-twake) for more detailed instructions.\n\n## using server api key\n\nto configure this credential, you'll need:\n\n- a **host url**: the url of your twake self-hosted instance.\n- a **public id**: generated when you create an app.\n- a **private api key**: generated when you create an app.\n\nto generate your **public id** and **private api key**, [create a twake application](https://doc.twake.app/developers-api/get-started/create-your-first-application):\n\n1. go to **workspace settings > applications and connectors > access your applications and connectors > create an application**.\n1. enter appropriate details.\n1. once you've created your app, view its **api details**.\n1. copy the **public identifier** and add it as the n8n **public id**.\n1. copy the **private key** and add it as the n8n **private api key**.\n\nrefer to [api settings](https://doc.twake.app/developers-api/get-started/create-your-first-application#id-3.-api-settings) for more information.\n twake credentials",
-        "importantTerms": [
-          "twake",
-          "create",
-          "your",
-          "https",
-          "application",
-          "credentials",
-          "public",
-          "private",
-          "nodes",
-          "cloud",
-          "refer",
-          "developers",
-          "more",
-          "configure",
-          "generated",
-          "when",
-          "applications",
-          "connectors",
-          "settings"
-        ]
-      }
-    },
     {
       "id": "page-0981",
       "title": "Twist credentials",
@@ -91205,7 +91258,7 @@
         "page-0029",
         "page-0030",
         "page-0031",
-        "page-0038",
+        "page-0039",
         "page-0051",
         "page-0152",
         "page-0545",
@@ -92171,6 +92224,7 @@
         "page-0094",
         "page-0110",
         "page-0211",
+        "page-0213",
         "page-0678",
         "page-0731",
         "page-1140",
@@ -92696,7 +92750,7 @@
         "page-0003",
         "page-0015",
         "page-0018",
-        "page-0038",
+        "page-0039",
         "page-0068",
         "page-0077",
         "page-0093",
@@ -93103,8 +93157,8 @@
         "page-0013",
         "page-0021",
         "page-0027",
-        "page-0035",
-        "page-0037",
+        "page-0036",
+        "page-0038",
         "page-0528",
         "page-0545",
         "page-0546",
@@ -93553,9 +93607,10 @@
       "memory": [
         "page-0003",
         "page-0006",
-        "page-0039",
+        "page-0035",
         "page-0041",
         "page-0137",
+        "page-0213",
         "page-0547",
         "page-0558",
         "page-0595",
@@ -94512,7 +94567,7 @@
         "page-0029",
         "page-0030",
         "page-0031",
-        "page-0038",
+        "page-0039",
         "page-0046",
         "page-0048",
         "page-0051",
@@ -95078,8 +95133,8 @@
       "vector": [
         "page-0006",
         "page-0023",
-        "page-0036",
-        "page-0038",
+        "page-0037",
+        "page-0039",
         "page-0041",
         "page-0515",
         "page-0545",
@@ -95198,7 +95253,7 @@
       "model": [
         "page-0006",
         "page-0019",
-        "page-0037",
+        "page-0038",
         "page-0535",
         "page-0543",
         "page-0558",
@@ -95699,7 +95754,7 @@
       "text": [
         "page-0009",
         "page-0023",
-        "page-0036",
+        "page-0037",
         "page-0041",
         "page-0069",
         "page-0138",
@@ -95861,7 +95916,7 @@
         "page-0836",
         "page-0844",
         "page-0944",
-        "page-0980",
+        "page-0979",
         "page-1180",
         "page-1197"
       ],
@@ -96202,6 +96257,7 @@
         "page-0021",
         "page-0069",
         "page-0134",
+        "page-0213",
         "page-0654",
         "page-0661",
         "page-0686",
@@ -96273,7 +96329,7 @@
         "page-0836",
         "page-0876",
         "page-0935",
-        "page-0980",
+        "page-0979",
         "page-0989",
         "page-0995",
         "page-0999",
@@ -96499,7 +96555,7 @@
         "page-0034",
         "page-0035",
         "page-0036",
-        "page-0039",
+        "page-0037",
         "page-0070",
         "page-0085",
         "page-0098",
@@ -97003,7 +97059,7 @@
       ],
       "power": [
         "page-0015",
-        "page-0036"
+        "page-0037"
       ],
       "feature": [
         "page-0015",
@@ -97021,8 +97077,8 @@
         "page-0029",
         "page-0030",
         "page-0031",
-        "page-0036",
-        "page-0038",
+        "page-0037",
+        "page-0039",
         "page-0050",
         "page-0108",
         "page-0109",
@@ -97302,6 +97358,7 @@
         "page-0063",
         "page-0067",
         "page-0140",
+        "page-0213",
         "page-0217",
         "page-0218",
         "page-0225",
@@ -98371,7 +98428,7 @@
       ],
       "templates": [
         "page-0017",
-        "page-0037",
+        "page-0038",
         "page-0061",
         "page-0139",
         "page-0233",
@@ -99019,7 +99076,7 @@
         "page-0964",
         "page-0969",
         "page-0976",
-        "page-0979",
+        "page-0980",
         "page-0983",
         "page-0991",
         "page-0992",
@@ -99102,7 +99159,7 @@
       "examples": [
         "page-0018",
         "page-0032",
-        "page-0037",
+        "page-0038",
         "page-0058",
         "page-0061",
         "page-0067",
@@ -99646,7 +99703,7 @@
         "page-0150",
         "page-0154",
         "page-0171",
-        "page-0213",
+        "page-0214",
         "page-0220",
         "page-1146",
         "page-1149",
@@ -99745,7 +99802,7 @@
       ],
       "tools": [
         "page-0021",
-        "page-0035",
+        "page-0036",
         "page-0041",
         "page-0203",
         "page-0528",
@@ -100239,7 +100296,8 @@
         "page-1246"
       ],
       "avoiding": [
-        "page-0027"
+        "page-0027",
+        "page-0213"
       ],
       "calculating": [
         "page-0027",
@@ -100333,7 +100391,7 @@
         "page-0033",
         "page-0034",
         "page-0035",
-        "page-0039",
+        "page-0036",
         "page-0076",
         "page-0077",
         "page-0078",
@@ -100348,26 +100406,29 @@
       "chain?": [
         "page-0034"
       ],
-      "tool?": [
+      "memory?": [
         "page-0035"
       ],
-      "database?": [
+      "tool?": [
         "page-0036"
       ],
+      "database?": [
+        "page-0037"
+      ],
       "databases?": [
-        "page-0036"
+        "page-0037"
       ],
       "simplified": [
-        "page-0036"
+        "page-0037"
       ],
       "demonstrating": [
-        "page-0036"
+        "page-0037"
       ],
       "similarity": [
-        "page-0036"
+        "page-0037"
       ],
       "search": [
-        "page-0036",
+        "page-0037",
         "page-0503",
         "page-0545",
         "page-0555",
@@ -100377,16 +100438,16 @@
         "page-1197"
       ],
       "embeddings,": [
-        "page-0036"
+        "page-0037"
       ],
       "retrievers,": [
-        "page-0036"
+        "page-0037"
       ],
       "splitters,": [
-        "page-0036"
+        "page-0037"
       ],
       "document": [
-        "page-0036",
+        "page-0037",
         "page-0041",
         "page-0509",
         "page-0510",
@@ -100394,11 +100455,11 @@
         "page-0570"
       ],
       "loaders": [
-        "page-0036",
+        "page-0037",
         "page-0041"
       ],
       "specify": [
-        "page-0037",
+        "page-0038",
         "page-0162",
         "page-0169",
         "page-0283",
@@ -100406,7 +100467,7 @@
         "page-0455"
       ],
       "parameters": [
-        "page-0037",
+        "page-0038",
         "page-0068",
         "page-0072",
         "page-0139",
@@ -100558,10 +100619,10 @@
         "page-1242"
       ],
       "fill": [
-        "page-0037"
+        "page-0038"
       ],
       "parameter": [
-        "page-0037",
+        "page-0038",
         "page-0704",
         "page-1153",
         "page-1161",
@@ -100569,24 +100630,24 @@
         "page-1221"
       ],
       "`$fromai()`": [
-        "page-0037",
+        "page-0038",
         "page-0564",
         "page-0613"
       ],
       "function": [
-        "page-0037"
+        "page-0038"
       ],
       "populate": [
-        "page-0038",
+        "page-0039",
         "page-0517"
       ],
       "pinecone": [
-        "page-0038",
+        "page-0039",
         "page-0551",
         "page-0910"
       ],
       "database": [
-        "page-0038",
+        "page-0039",
         "page-0137",
         "page-0153",
         "page-0156",
@@ -100607,12 +100668,9 @@
         "page-0972"
       ],
       "website": [
-        "page-0038",
+        "page-0039",
         "page-0713"
       ],
-      "memory?": [
-        "page-0039"
-      ],
       "stores": [
         "page-0041"
       ],
@@ -102728,7 +102786,7 @@
         "page-0975",
         "page-0976",
         "page-0977",
-        "page-0980",
+        "page-0979",
         "page-0981",
         "page-0982",
         "page-0984",
@@ -104255,7 +104313,7 @@
         "page-0967",
         "page-0974",
         "page-0977",
-        "page-0979",
+        "page-0980",
         "page-0992",
         "page-0997",
         "page-0998",
@@ -104368,7 +104426,7 @@
         "page-0710",
         "page-0824",
         "page-0892",
-        "page-0979",
+        "page-0980",
         "page-1161",
         "page-1175",
         "page-1176",
@@ -104588,7 +104646,7 @@
       ],
       "scaling": [
         "page-0167",
-        "page-0213",
+        "page-0214",
         "page-0216"
       ],
       "jobs": [
@@ -105291,6 +105349,7 @@
       ],
       "reduce": [
         "page-0211",
+        "page-0213",
         "page-1184"
       ],
       "ending": [
@@ -105355,6 +105414,25 @@
       "storing": [
         "page-0212"
       ],
+      "identifying": [
+        "page-0213"
+      ],
+      "situations": [
+        "page-0213"
+      ],
+      "typical": [
+        "page-0213"
+      ],
+      "causes": [
+        "page-0213"
+      ],
+      "increase": [
+        "page-0213"
+      ],
+      "consumption": [
+        "page-0213",
+        "page-1184"
+      ],
       "benchmarking": [
         "page-0215"
       ],
@@ -107137,11 +107215,11 @@
       ],
       "twake": [
         "page-0459",
-        "page-0980"
+        "page-0979"
       ],
       "twilio": [
         "page-0460",
-        "page-0979",
+        "page-0980",
         "page-1106",
         "page-1197"
       ],
@@ -109279,7 +109357,7 @@
       ],
       "selecting": [
         "page-0853",
-        "page-0979",
+        "page-0980",
         "page-1240"
       ],
       "domains": [
@@ -110025,9 +110103,6 @@
       "offline": [
         "page-1183"
       ],
-      "consumption": [
-        "page-1184"
-      ],
       "incident": [
         "page-1184",
         "page-1193"
@@ -111274,6 +111349,7 @@
         "page-0211",
         "page-0212",
         "page-0213",
+        "page-0214",
         "page-0215",
         "page-0216",
         "page-0217",