You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, you can pass execution labels when starting an execution from the UI/API or a Webhook.
But you cannot do that from a Trigger as triggers automatically start executions so the list of labels is static and not dynamic.
But there is interesting use case for that, for example to add some identifier in a label extracted from the trigger message.
What we can do is to allow to define dynamic labels in a trigger that will allow using Pebble expression so the trigger output will be available to create the labels.
@anna-geller we cannot do as you propose as flow labels are static labels not dynamic, we copy flow labels into the execution at run time but flow labels are also used to filter flows for ex.
Feature description
Currently, you can pass execution labels when starting an execution from the UI/API or a Webhook.
But you cannot do that from a Trigger as triggers automatically start executions so the list of labels is static and not dynamic.
But there is interesting use case for that, for example to add some identifier in a label extracted from the trigger message.
What we can do is to allow to define dynamic labels in a trigger that will allow using Pebble expression so the trigger output will be available to create the labels.
For example:
The text was updated successfully, but these errors were encountered: