@n8n-as-code/skills 2.1.0 → 2.1.1-next.3

package/dist/assets/n8n-credentials-ontology.json

@@ -1,5 +1,5 @@
 {
-  "generatedAt": "2026-05-11T13:29:18.922Z",
+  "generatedAt": "2026-05-11T16:02:15.142Z",
   "n8nVersion": "unknown",
   "sourceFileCount": 428,
   "scanDirectories": [

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

@@ -1,11 +1,11 @@
 {
-  "generatedAt": "2026-05-11T13:29:19.741Z",
+  "generatedAt": "2026-05-11T16:02:16.013Z",
   "version": "1.0.0",
   "sourceUrl": "https://docs.n8n.io/llms.txt",
-  "totalPages": 1278,
+  "totalPages": 1279,
   "statistics": {
     "byCategory": {
-      "other": 513,
+      "other": 514,
       "tutorials": 27,
       "advanced-ai": 28,
       "api": 6,
@@ -26,7 +26,7 @@
   "categories": {
     "other": {
       "description": "General documentation and guides",
-      "totalPages": 513,
+      "totalPages": 514,
       "pages": [
         "page-0001",
         "page-0002",
@@ -49,6 +49,7 @@
         "page-0237",
         "page-0238",
         "page-0239",
+        "page-0240",
         "page-0654",
         "page-0655",
         "page-0656",
@@ -20762,13 +20763,13 @@
       "nodeName": null,
       "nodeType": null,
       "content": {
-        "markdown": "# Handling API rate limits\n\n[API](../../../glossary/#api) rate limits are restrictions on request frequency. For example, an API may limit the number of requests you can make per minute, or per day.\n\nAPIs can also limits how much data you can send in one request, or how much data the API sends in a single response.\n\n## Identify rate limit issues\n\nWhen an n8n node hits a rate limit, it errors. n8n displays the error message in the node output panel. This includes the error message from the service.\n\nIf n8n received error 429 (too many requests) from the service, the error message is **The service is receiving too many requests from you**.\n\nTo check the rate limits for the service you're using, refer to the API documentation for the service.\n\n## Handle rate limits for integrations\n\nThere are two ways to handle rate limits in n8n's integrations: using the Retry On Fail setting, or using a combination of the [Loop Over Items](../core-nodes/n8n-nodes-base.splitinbatches/) and [Wait](../core-nodes/n8n-nodes-base.wait/) nodes:\n\n- Retry On Fail adds a pause between API request attempts.\n- With Loop Over Items and Wait you can break you request data into smaller chunks, as well as pausing between requests.\n\n### Enable Retry On Fail\n\nWhen you enable Retry On Fail, the node automatically tries the request again if it fails the first time.\n\n1. Open the node.\n1. Select **Settings**.\n1. Enable the **Retry On Fail** toggle.\n1. Configure the retry settings: if using this to work around rate limits, set **Wait Between Tries (ms)** to more than the rate limit. For example, if the API you're using allows one request per second, set **Wait Between Tries (ms)** to `1000` to allow a 1 second wait.\n\n### Use Loop Over Items and Wait\n\nUse the Loop Over Items node to batch the input items, and the Wait node to introduce a pause between each request.\n\n1. Add the Loop Over Items node before the node that calls the API. Refer to [Loop Over Items](../core-nodes/n8n-nodes-base.splitinbatches/) for information on how to configure the node.\n1. Add the Wait node after the node that calls the API, and connect it back to the Loop Over Items node. Refer to [Wait](../core-nodes/n8n-nodes-base.wait/) for information on how to configure the node.\n\nFor example, to handle rate limits when using OpenAI:\n\n## Handle rate limits in the HTTP Request node\n\nThe HTTP Request node has built-in settings for handling rate limits and large amounts of data.\n\n### Batch requests\n\nUse the Batching option to send more than one request, reducing the request size, and introducing a pause between requests. This is the equivalent of using Loop Over Items and Wait.\n\n1. In the HTTP Request node, select **Add Option** > **Batching**.\n1. Set **Items per Batch**: this is the number of input items to include in each request.\n1. Set **Batch Interval (ms)** to introduce a delay between requests. For example, if the API you're using allows one request per second, set **Wait Between Tries (ms)** to `1000` to allow a 1 second wait.\n\n### Paginate results\n\nAPIs paginate their results when they need to send more data than they can handle in a single response. For more information on pagination in the HTTP Request node, refer to [HTTP Request node | Pagination](../core-nodes/n8n-nodes-base.httprequest/#pagination).\n",
-        "excerpt": "# Handling API rate limits  [API](../../../glossary/#api) rate limits are restrictions on request frequency. For example, an API may limit the number of requests you can make per minute, or per day.  APIs can also limits how much data you can send in one request, or how much data the API sends in a single response.  ## Identify rate limit issues  When an n8n node hits a rate limit, it errors. n8n displays the error message in the node output panel. This includes the error message from the servic...",
+        "markdown": "# Built-in integrations\n\nThis section contains the [node](../../../glossary/#node-n8n) library: reference documentation for every built-in node in n8n, and their credentials.\n\n## Node operations: Triggers and Actions\n\nWhen you add a node to a workflow, n8n displays a list of available operations. An operation is something a node does, such as getting or sending data.\n\nThere are two types of operation:\n\n- Triggers start a workflow in response to specific events or conditions in your services. When you select a Trigger, n8n adds a trigger node to your workflow, with the Trigger operation you chose pre-selected. When you search for a node in n8n, Trigger operations have a bolt icon .\n- Actions are operations that represent specific tasks within a workflow, which you can use to manipulate data, perform operations on external systems, and trigger events in other systems as part of your workflows. When you select an Action, n8n adds a node to your workflow, with the Action operation you chose pre-selected.\n\n## Core nodes\n\nCore nodes can be actions or [triggers](../../../glossary/#trigger-node-n8n). Whereas most nodes connect to a specific external service, core nodes provide functionality such as logic, scheduling, or generic API calls.\n\n## Cluster nodes\n\n[Cluster nodes](../../../glossary/#cluster-node-n8n) are node groups that work together to provide functionality in an n8n workflow. Instead of using a single node, you use a [root node](../../../glossary/#root-node-n8n) and one or more [sub-nodes](../../../glossary/#sub-node-n8n) that extend the functionality of the node.\n\n## Credentials\n\nExternal services need a way to identify and authenticate users. This data can range from an API key over an email/password combination to a long multi-line private key. You can save these in n8n as [credentials](../../../glossary/#credential-n8n).\n\nNodes in n8n can then request that credential information. As another layer of security, only node types with specific access rights can access the credentials.\n\nTo make sure that the data is secure, it gets saved to the database encrypted. n8n uses a random personal encryption key, which it automatically generates on the first run of n8n and then saved under `~/.n8n/config`.\n\nTo learn more about creating, managing, and sharing credentials, refer to [Manage credentials](../../../credentials/).\n\n## Community nodes\n\nn8n supports custom nodes built by the community. Refer to [Community nodes](../../community-nodes/installation/) for guidance on installing and using these nodes.\n\nFor help building your own custom nodes, and publish them to [npm](https://www.npmjs.com/), refer to [Creating nodes](../../creating-nodes/overview/) for more information.\n",
+        "excerpt": "# Built-in integrations  This section contains the [node](../../../glossary/#node-n8n) library: reference documentation for every built-in node in n8n, and their credentials.  ## Node operations: Triggers and Actions  When you add a node to a workflow, n8n displays a list of available operations. An operation is something a node does, such as getting or sending data.  There are two types of operation:  - Triggers start a workflow in response to specific events or conditions in your services. Whe...",
         "sections": [
           {
-            "title": "Handling API rate limits",
+            "title": "Built-in integrations",
             "level": 1,
-            "content": "[API](../../../glossary/#api) rate limits are restrictions on request frequency. For example, an API may limit the number of requests you can make per minute, or per day.\n\nAPIs can also limits how much data you can send in one request, or how much data the API sends in a single response."
+            "content": "This section contains the [node](../../../glossary/#node-n8n) library: reference documentation for every built-in node in n8n, and their credentials."
           }
         ]
       },
@@ -20788,6 +20789,97 @@
           "community"
         ],
         "useCases": [],
+        "operations": [
+          "triggers",
+          "actions",
+          "n8n adds a trigger node to your workflow",
+          "trigger operations have a bolt icon .",
+          "node : triggers and"
+        ],
+        "codeExamples": 0,
+        "complexity": "beginner",
+        "readingTime": "2 min",
+        "contentLength": 2719,
+        "relatedPages": []
+      },
+      "searchIndex": {
+        "fullText": "node types # built-in integrations\n\nthis section contains the [node](../../../glossary/#node-n8n) library: reference documentation for every built-in node in n8n, and their credentials.\n\n## node operations: triggers and actions\n\nwhen you add a node to a workflow, n8n displays a list of available operations. an operation is something a node does, such as getting or sending data.\n\nthere are two types of operation:\n\n- triggers start a workflow in response to specific events or conditions in your services. when you select a trigger, n8n adds a trigger node to your workflow, with the trigger operation you chose pre-selected. when you search for a node in n8n, trigger operations have a bolt icon .\n- actions are operations that represent specific tasks within a workflow, which you can use to manipulate data, perform operations on external systems, and trigger events in other systems as part of your workflows. when you select an action, n8n adds a node to your workflow, with the action operation you chose pre-selected.\n\n## core nodes\n\ncore nodes can be actions or [triggers](../../../glossary/#trigger-node-n8n). whereas most nodes connect to a specific external service, core nodes provide functionality such as logic, scheduling, or generic api calls.\n\n## cluster nodes\n\n[cluster nodes](../../../glossary/#cluster-node-n8n) are node groups that work together to provide functionality in an n8n workflow. instead of using a single node, you use a [root node](../../../glossary/#root-node-n8n) and one or more [sub-nodes](../../../glossary/#sub-node-n8n) that extend the functionality of the node.\n\n## credentials\n\nexternal services need a way to identify and authenticate users. this data can range from an api key over an email/password combination to a long multi-line private key. you can save these in n8n as [credentials](../../../glossary/#credential-n8n).\n\nnodes in n8n can then request that credential information. as another layer of security, only node types with specific access rights can access the credentials.\n\nto make sure that the data is secure, it gets saved to the database encrypted. n8n uses a random personal encryption key, which it automatically generates on the first run of n8n and then saved under `~/.n8n/config`.\n\nto learn more about creating, managing, and sharing credentials, refer to [manage credentials](../../../credentials/).\n\n## community nodes\n\nn8n supports custom nodes built by the community. refer to [community nodes](../../community-nodes/installation/) for guidance on installing and using these nodes.\n\nfor help building your own custom nodes, and publish them to [npm](https://www.npmjs.com/), refer to [creating nodes](../../creating-nodes/overview/) for more information.\n built-in integrations",
+        "importantTerms": [
+          "node",
+          "nodes",
+          "credentials",
+          "glossary",
+          "workflow",
+          "trigger",
+          "operations",
+          "your",
+          "that",
+          "built",
+          "when",
+          "operation",
+          "data",
+          "specific",
+          "community",
+          "types",
+          "triggers",
+          "actions",
+          "with",
+          "external",
+          "core",
+          "functionality",
+          "cluster",
+          "more",
+          "creating",
+          "refer"
+        ]
+      }
+    },
+    {
+      "id": "page-0240",
+      "title": "Handle rate limits",
+      "url": "https://docs.n8n.io/integrations/builtin/rate-limits/index.md",
+      "urlPath": "integrations/builtin/rate-limits/index.md",
+      "category": "other",
+      "subcategory": null,
+      "nodeName": null,
+      "nodeType": null,
+      "content": {
+        "markdown": "# Handling API rate limits\n\n[API](../../../glossary/#api) rate limits are restrictions on request frequency. For example, an API may limit the number of requests you can make per minute, or per day.\n\nAPIs can also limits how much data you can send in one request, or how much data the API sends in a single response.\n\n## Identify rate limit issues\n\nWhen an n8n node hits a rate limit, it errors. n8n displays the error message in the node output panel. This includes the error message from the service.\n\nIf n8n received error 429 (too many requests) from the service, the error message is **The service is receiving too many requests from you**.\n\nTo check the rate limits for the service you're using, refer to the API documentation for the service.\n\n## Handle rate limits for integrations\n\nThere are two ways to handle rate limits in n8n's integrations: using the Retry On Fail setting, or using a combination of the [Loop Over Items](../core-nodes/n8n-nodes-base.splitinbatches/) and [Wait](../core-nodes/n8n-nodes-base.wait/) nodes:\n\n- Retry On Fail adds a pause between API request attempts.\n- With Loop Over Items and Wait you can break you request data into smaller chunks, as well as pausing between requests.\n\n### Enable Retry On Fail\n\nWhen you enable Retry On Fail, the node automatically tries the request again if it fails the first time.\n\n1. Open the node.\n1. Select **Settings**.\n1. Enable the **Retry On Fail** toggle.\n1. Configure the retry settings: if using this to work around rate limits, set **Wait Between Tries (ms)** to more than the rate limit. For example, if the API you're using allows one request per second, set **Wait Between Tries (ms)** to `1000` to allow a 1 second wait.\n\n### Use Loop Over Items and Wait\n\nUse the Loop Over Items node to batch the input items, and the Wait node to introduce a pause between each request.\n\n1. Add the Loop Over Items node before the node that calls the API. Refer to [Loop Over Items](../core-nodes/n8n-nodes-base.splitinbatches/) for information on how to configure the node.\n1. Add the Wait node after the node that calls the API, and connect it back to the Loop Over Items node. Refer to [Wait](../core-nodes/n8n-nodes-base.wait/) for information on how to configure the node.\n\nFor example, to handle rate limits when using OpenAI:\n\n## Handle rate limits in the HTTP Request node\n\nThe HTTP Request node has built-in settings for handling rate limits and large amounts of data.\n\n### Batch requests\n\nUse the Batching option to send more than one request, reducing the request size, and introducing a pause between requests. This is the equivalent of using Loop Over Items and Wait.\n\n1. In the HTTP Request node, select **Add Option** > **Batching**.\n1. Set **Items per Batch**: this is the number of input items to include in each request.\n1. Set **Batch Interval (ms)** to introduce a delay between requests. For example, if the API you're using allows one request per second, set **Wait Between Tries (ms)** to `1000` to allow a 1 second wait.\n\n### Paginate results\n\nAPIs paginate their results when they need to send more data than they can handle in a single response. For more information on pagination in the HTTP Request node, refer to [HTTP Request node | Pagination](../core-nodes/n8n-nodes-base.httprequest/#pagination).\n",
+        "excerpt": "# Handling API rate limits  [API](../../../glossary/#api) rate limits are restrictions on request frequency. For example, an API may limit the number of requests you can make per minute, or per day.  APIs can also limits how much data you can send in one request, or how much data the API sends in a single response.  ## Identify rate limit issues  When an n8n node hits a rate limit, it errors. n8n displays the error message in the node output panel. This includes the error message from the servic...",
+        "sections": [
+          {
+            "title": "Handling API rate limits",
+            "level": 1,
+            "content": "[API](../../../glossary/#api) rate limits are restrictions on request frequency. For example, an API may limit the number of requests you can make per minute, or per day.\n\nAPIs can also limits how much data you can send in one request, or how much data the API sends in a single response."
+          }
+        ]
+      },
+      "metadata": {
+        "keywords": [
+          "handle",
+          "rate",
+          "limits",
+          "handling",
+          "identify",
+          "limit",
+          "issues",
+          "integrations",
+          "enable",
+          "retry",
+          "fail",
+          "loop",
+          "over",
+          "items",
+          "wait",
+          "http",
+          "request",
+          "node",
+          "batch",
+          "requests",
+          "paginate",
+          "results"
+        ],
+        "useCases": [],
         "operations": [],
         "codeExamples": 0,
         "complexity": "beginner",
@@ -20796,12 +20888,12 @@
         "relatedPages": []
       },
       "searchIndex": {
-        "fullText": "node types # handling api rate limits\n\n[api](../../../glossary/#api) rate limits are restrictions on request frequency. for example, an api may limit the number of requests you can make per minute, or per day.\n\napis can also limits how much data you can send in one request, or how much data the api sends in a single response.\n\n## identify rate limit issues\n\nwhen an n8n node hits a rate limit, it errors. n8n displays the error message in the node output panel. this includes the error message from the service.\n\nif n8n received error 429 (too many requests) from the service, the error message is **the service is receiving too many requests from you**.\n\nto check the rate limits for the service you're using, refer to the api documentation for the service.\n\n## handle rate limits for integrations\n\nthere are two ways to handle rate limits in n8n's integrations: using the retry on fail setting, or using a combination of the [loop over items](../core-nodes/n8n-nodes-base.splitinbatches/) and [wait](../core-nodes/n8n-nodes-base.wait/) nodes:\n\n- retry on fail adds a pause between api request attempts.\n- with loop over items and wait you can break you request data into smaller chunks, as well as pausing between requests.\n\n### enable retry on fail\n\nwhen you enable retry on fail, the node automatically tries the request again if it fails the first time.\n\n1. open the node.\n1. select **settings**.\n1. enable the **retry on fail** toggle.\n1. configure the retry settings: if using this to work around rate limits, set **wait between tries (ms)** to more than the rate limit. for example, if the api you're using allows one request per second, set **wait between tries (ms)** to `1000` to allow a 1 second wait.\n\n### use loop over items and wait\n\nuse the loop over items node to batch the input items, and the wait node to introduce a pause between each request.\n\n1. add the loop over items node before the node that calls the api. refer to [loop over items](../core-nodes/n8n-nodes-base.splitinbatches/) for information on how to configure the node.\n1. add the wait node after the node that calls the api, and connect it back to the loop over items node. refer to [wait](../core-nodes/n8n-nodes-base.wait/) for information on how to configure the node.\n\nfor example, to handle rate limits when using openai:\n\n## handle rate limits in the http request node\n\nthe http request node has built-in settings for handling rate limits and large amounts of data.\n\n### batch requests\n\nuse the batching option to send more than one request, reducing the request size, and introducing a pause between requests. this is the equivalent of using loop over items and wait.\n\n1. in the http request node, select **add option** > **batching**.\n1. set **items per batch**: this is the number of input items to include in each request.\n1. set **batch interval (ms)** to introduce a delay between requests. for example, if the api you're using allows one request per second, set **wait between tries (ms)** to `1000` to allow a 1 second wait.\n\n### paginate results\n\napis paginate their results when they need to send more data than they can handle in a single response. for more information on pagination in the http request node, refer to [http request node | pagination](../core-nodes/n8n-nodes-base.httprequest/#pagination).\n handling api rate limits",
+        "fullText": "handle rate limits # handling api rate limits\n\n[api](../../../glossary/#api) rate limits are restrictions on request frequency. for example, an api may limit the number of requests you can make per minute, or per day.\n\napis can also limits how much data you can send in one request, or how much data the api sends in a single response.\n\n## identify rate limit issues\n\nwhen an n8n node hits a rate limit, it errors. n8n displays the error message in the node output panel. this includes the error message from the service.\n\nif n8n received error 429 (too many requests) from the service, the error message is **the service is receiving too many requests from you**.\n\nto check the rate limits for the service you're using, refer to the api documentation for the service.\n\n## handle rate limits for integrations\n\nthere are two ways to handle rate limits in n8n's integrations: using the retry on fail setting, or using a combination of the [loop over items](../core-nodes/n8n-nodes-base.splitinbatches/) and [wait](../core-nodes/n8n-nodes-base.wait/) nodes:\n\n- retry on fail adds a pause between api request attempts.\n- with loop over items and wait you can break you request data into smaller chunks, as well as pausing between requests.\n\n### enable retry on fail\n\nwhen you enable retry on fail, the node automatically tries the request again if it fails the first time.\n\n1. open the node.\n1. select **settings**.\n1. enable the **retry on fail** toggle.\n1. configure the retry settings: if using this to work around rate limits, set **wait between tries (ms)** to more than the rate limit. for example, if the api you're using allows one request per second, set **wait between tries (ms)** to `1000` to allow a 1 second wait.\n\n### use loop over items and wait\n\nuse the loop over items node to batch the input items, and the wait node to introduce a pause between each request.\n\n1. add the loop over items node before the node that calls the api. refer to [loop over items](../core-nodes/n8n-nodes-base.splitinbatches/) for information on how to configure the node.\n1. add the wait node after the node that calls the api, and connect it back to the loop over items node. refer to [wait](../core-nodes/n8n-nodes-base.wait/) for information on how to configure the node.\n\nfor example, to handle rate limits when using openai:\n\n## handle rate limits in the http request node\n\nthe http request node has built-in settings for handling rate limits and large amounts of data.\n\n### batch requests\n\nuse the batching option to send more than one request, reducing the request size, and introducing a pause between requests. this is the equivalent of using loop over items and wait.\n\n1. in the http request node, select **add option** > **batching**.\n1. set **items per batch**: this is the number of input items to include in each request.\n1. set **batch interval (ms)** to introduce a delay between requests. for example, if the api you're using allows one request per second, set **wait between tries (ms)** to `1000` to allow a 1 second wait.\n\n### paginate results\n\napis paginate their results when they need to send more data than they can handle in a single response. for more information on pagination in the http request node, refer to [http request node | pagination](../core-nodes/n8n-nodes-base.httprequest/#pagination).\n handling api rate limits",
         "importantTerms": [
           "node",
           "request",
-          "wait",
           "rate",
+          "wait",
           "limits",
           "items",
           "nodes",
@@ -20810,10 +20902,10 @@
           "over",
           "between",
           "requests",
+          "handle",
           "retry",
           "data",
           "service",
-          "handle",
           "fail",
           "core",
           "base",
@@ -94290,6 +94382,7 @@
         "page-0218",
         "page-0230",
         "page-0239",
+        "page-0240",
         "page-0242",
         "page-0243",
         "page-0244",
@@ -95480,6 +95573,7 @@
         "page-0070",
         "page-0079",
         "page-0080",
+        "page-0240",
         "page-0506",
         "page-0540",
         "page-0544",
@@ -95565,6 +95659,7 @@
         "page-0012",
         "page-0026",
         "page-0102",
+        "page-0240",
         "page-0355",
         "page-0381",
         "page-0501",
@@ -96101,6 +96196,7 @@
         "page-0224",
         "page-0226",
         "page-0233",
+        "page-0240",
         "page-0577",
         "page-0580",
         "page-0883",
@@ -99982,6 +100078,7 @@
         "page-0013",
         "page-0020",
         "page-0138",
+        "page-0240",
         "page-0699"
       ],
       "calls": [
@@ -102372,6 +102469,7 @@
         "page-0018",
         "page-0066",
         "page-0136",
+        "page-0240",
         "page-0687",
         "page-1156",
         "page-1179",
@@ -102881,6 +102979,7 @@
       "results": [
         "page-0024",
         "page-0026",
+        "page-0240",
         "page-0558",
         "page-0559",
         "page-0560",
@@ -104538,6 +104637,7 @@
       ],
       "limits": [
         "page-0052",
+        "page-0240",
         "page-1006",
         "page-1208",
         "page-1211"
@@ -105429,6 +105529,7 @@
         "page-0070",
         "page-0079",
         "page-0080",
+        "page-0240",
         "page-0635",
         "page-0678",
         "page-0707",
@@ -105443,6 +105544,7 @@
       ],
       "requests": [
         "page-0053",
+        "page-0240",
         "page-0422",
         "page-0502",
         "page-0544",
@@ -105527,6 +105629,7 @@
         "page-0111",
         "page-0112",
         "page-0138",
+        "page-0240",
         "page-0683",
         "page-0687",
         "page-0699",
@@ -109613,6 +109716,7 @@
       "integrations": [
         "page-0236",
         "page-0239",
+        "page-0240",
         "page-0891",
         "page-0914"
       ],
@@ -109969,6 +110073,54 @@
         "page-0239",
         "page-1270"
       ],
+      "handle": [
+        "page-0240",
+        "page-0527"
+      ],
+      "rate": [
+        "page-0240",
+        "page-1006"
+      ],
+      "identify": [
+        "page-0240"
+      ],
+      "limit": [
+        "page-0240",
+        "page-0568",
+        "page-0576",
+        "page-0640",
+        "page-0683",
+        "page-0707",
+        "page-0813",
+        "page-1221"
+      ],
+      "retry": [
+        "page-0240",
+        "page-0723",
+        "page-1273",
+        "page-1279"
+      ],
+      "fail": [
+        "page-0240",
+        "page-0723"
+      ],
+      "over": [
+        "page-0240",
+        "page-0699"
+      ],
+      "wait": [
+        "page-0240",
+        "page-0509",
+        "page-0538",
+        "page-0707"
+      ],
+      "batch": [
+        "page-0240",
+        "page-0699"
+      ],
+      "paginate": [
+        "page-0240"
+      ],
       "action": [
         "page-0242",
         "page-0538",
@@ -111446,11 +111598,6 @@
         "page-0538",
         "page-0696"
       ],
-      "wait": [
-        "page-0509",
-        "page-0538",
-        "page-0707"
-      ],
       "thread": [
         "page-0510"
       ],
@@ -111585,9 +111732,6 @@
         "page-0527",
         "page-1271"
       ],
-      "handle": [
-        "page-0527"
-      ],
       "null": [
         "page-0527"
       ],
@@ -112130,15 +112274,6 @@
       "fusion": [
         "page-0568"
       ],
-      "limit": [
-        "page-0568",
-        "page-0576",
-        "page-0640",
-        "page-0683",
-        "page-0707",
-        "page-0813",
-        "page-1221"
-      ],
       "alpha": [
         "page-0568",
         "page-1221"
@@ -112838,18 +112973,12 @@
       "arrays": [
         "page-0697"
       ],
-      "over": [
-        "page-0699"
-      ],
       "(split": [
         "page-0699"
       ],
       "batches)": [
         "page-0699"
       ],
-      "batch": [
-        "page-0699"
-      ],
       "reset": [
         "page-0699"
       ],
@@ -113002,14 +113131,6 @@
       "could": [
         "page-0723"
       ],
-      "retry": [
-        "page-0723",
-        "page-1273",
-        "page-1279"
-      ],
-      "fail": [
-        "page-0723"
-      ],
       "duplicates": [
         "page-0724",
         "page-0725",
@@ -113453,9 +113574,6 @@
       "trellix": [
         "page-1001"
       ],
-      "rate": [
-        "page-1006"
-      ],
       "typeform": [
         "page-1007",
         "page-1131"
@@ -114590,6 +114708,7 @@
         "page-0237",
         "page-0238",
         "page-0239",
+        "page-0240",
         "page-0654",
         "page-0655",
         "page-0656",