From 44159af83eb3fe834f5fe3842ce088612df99337 Mon Sep 17 00:00:00 2001 From: Faruk AYDIN Date: Wed, 9 Nov 2022 23:36:36 +0100 Subject: [PATCH] docs: Expands the explanation of already procesed control --- packages/docs/pages/build-integrations/triggers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/packages/docs/pages/build-integrations/triggers.md b/packages/docs/pages/build-integrations/triggers.md index 20c955f4..dcd695f1 100644 --- a/packages/docs/pages/build-integrations/triggers.md +++ b/packages/docs/pages/build-integrations/triggers.md @@ -136,7 +136,7 @@ We do not have to return anything from the `run` function. We are using the `$.p :::tip -`$.pushTriggerItem` is smart enough to understand if the data is already pushed to Automatisch or not. If the data is already pushed, it will stop the trigger, otherwise, it will continue to fetch new data. +`$.pushTriggerItem` is smart enough to understand if the data is already pushed to Automatisch or not. If the data is already pushed and processed, it will stop the trigger, otherwise, it will continue to fetch new data. The check is done by comparing the `internalId` field with the `internalId` field of the data that is already processed. The control of whether the data is already processed or not is scoped by the flow. :::