From b5fdcc28e086a8af9c9ebda0215bb2ac8fe96df8 Mon Sep 17 00:00:00 2001 From: Justin Ellingwood Date: Mon, 27 Jan 2025 15:16:12 +0000 Subject: [PATCH] Add character limits to Execution Data node (#2789) --- .../builtin/core-nodes/n8n-nodes-base.executiondata.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/integrations/builtin/core-nodes/n8n-nodes-base.executiondata.md b/docs/integrations/builtin/core-nodes/n8n-nodes-base.executiondata.md index 0e9bc9de7..07957d259 100644 --- a/docs/integrations/builtin/core-nodes/n8n-nodes-base.executiondata.md +++ b/docs/integrations/builtin/core-nodes/n8n-nodes-base.executiondata.md @@ -24,6 +24,15 @@ Available on Pro and Enterprise plans. Add a **Saved Field** for each key/value pair of metadata you'd like to save. +## Limitations + +The Execution Data node has the following restrictions when storing execution metadata: + +* `key`: limited to 50 characters +* `value`: limited to 512 characters + +If either the `key` or `value` exceed the above limitations, n8n truncates to their maximum length and outputs a log entry. + ## Templates and examples