FromPipelineTriggerEvent@1

The FromPipelineTriggerEvent@1 node is used to extract data from a pipeline trigger event and trigger the execution of the transformation pipeline.

This event is triggered by using pipeline triggers. See Pipeline Triggers for more information.

Adapter Prerequisites

• Mesh Adapter

Node Configuration

For fields path, targetPath, targetValueWriteMode, and targetValueKind, see Overview.

triggers:
  - type: FromPipelineTriggerEvent@1 # The pipeline will be triggered by a pipeline trigger event

Field	Type	Default	Description
allowConcurrentExecution	bool	false	Opt-out of the overlap protection described below. true executes every queued tick, several at once if they piled up.

triggers:
  - type: FromPipelineTriggerEvent@1
    allowConcurrentExecution: true # only for pipelines whose runs are independent and safe to overlap

Missed Ticks and Overlapping Runs

Each tick of a pipeline trigger is delivered into a durable queue per pipeline. If the Mesh Adapter is down, hibernated (on-demand lifecycle) or still busy with the previous run, ticks wait in that queue.

By default the node consumes the queue one tick at a time and coalesces a backlog into a single run: when it picks up a tick while newer ticks are already waiting, it skips the older one. After a 20-hour adapter outage an hourly pipeline therefore runs once when the adapter comes back — not 20 times in parallel — and a pipeline never runs concurrently with itself through its trigger. Ticks that arrive while a run is in progress result in exactly one follow-up run. The adapter log reports how many ticks were coalesced into a run.

Set allowConcurrentExecution: true only if every tick must be processed individually and the runs may overlap.