Why my MetricBase Flow was not triggering when conditions are met?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-14-2023 09:40 AM
2 REPLIES 2
Community Alums
Not applicable
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-15-2023 07:55 AM
Hi @celinenrmn ,
Please follow the steps to create the Metricbase Trigger and check your conditions properly:
- Navigate to All > Process Automation > Flow Designer.
- Click + New > New Flow.
- Define the flow properties.
For more information, see Create a flow.
- In the Trigger section, add a trigger and select MetricBase.
- Complete the trigger fields.
Field Description MetricBase Trigger Select or create a MetricBase trigger record to start the flow. For types of MetricBase triggers, see MetricBase triggers. Table Read-only table that contains the metric. Condition Click Add filters to set field-based conditions that determine when the flow runs. Condition Script Define a script in the Additional MetricBase Trigger Filtering and Moderation table to prevent duplicate metric events from re-triggering a flow. For example, if a metric hovers at a defined trigger threshold, create a script that defines whether to run the flow once when the metric is met, or every time the triggering threshold is exceeded. - Add actions, subflows, and flow logic to the flow.
- Test the flow.
Once behaving as desired, activate the flow. For more information, see Test a flow and Activate a flow.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-15-2023 11:23 AM
Sandeep,
Hi Sandeep,
Thank you for the very detailed reply. In our scenario, it is possible that the metric hovers above the threshold for a while. Would repeated trigger events stopped the execution of the flow? Do you have an example for how to stop this using Condition Script? That is probably what I need.