Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hey Folks, question about SLAs - is it possible to trigger a flow run in case a certain flow run fails ?

Our use case is we want to run a “clean up flow” run if a given flow run fails …

Using a flow state handler is not ideal for us since the state handler will not run in case the flow run fails due to resource exhaustion

hey, yes that’s definitely possible and there are several ways how you could approach that. Are you on Prefect Cloud?

<@U0141PE1A84> regarding this point:
&gt; in case the flow run fails due to resource exhaustion
if your infrastructure crashes in the middle of a flow run, then it’s possible that the Flow’s heartbeat dies with it. In this scenario, it would be much more difficult to take action based on failure since the backend may think that your flow run is still in progress. This is also hard to answer without knowing your infrastructure, because it heavily dependent on where and how you run and configure your agent, run config, etc.

Screen Shot 2021-11-23 at 11.57.33 AM.png

Hi <@U02H1A95XDW> - Yes I am on prefect cloud but I don’t see creating a flow run as a possible action under the automations tab
Please see the attached screenshot

Screen Shot 2021-11-23 at 12.06.12 PM.png

I specifically mean under actions I only sending message actions …

Does that mean I need to create a custom action which “creates a flow run”  ? I thought it would be one of the default options available

A bit about our infra - we are running a kubernetes agent and a DaskExecutor on AWS EKS

You’re right, this is not yet under Automations in the UI, but it should be added in the future, there is <https://github.com/PrefectHQ/ui/issues/1140|an open PR> for it.

is there a graphql snippet you can share that would create this action ? (that would be nice if it is something readily available)

There is a “create_action” mutation but I don’t know atm how the query would need to look like.

```mutation {
  create_action(input: {config: {create_flow_run: {flow_group_id: "..."}}}) {
    id
  }
}```

If you use the IAPI in the UI you can see all of the options for the config

```flow_group_id: UUID!

The flow group id to create a flow run for
parameters: JSON

Optional parameters to pass to the flow run
in_seconds: Int

An optional amount of time to wait before starting the flow run
run_name: String

An optional name for the flow run
labels: [String]

An optional list of labels for the flow run
idempotency_key: String

An optional key to prevent duplicate runs from being created```

Once you’ve got an `action_id`, you can create a hook to the relevant event with `create_flow_sla_failed_hook` or `create_flow_run_state_changed_hook`

You can also set parameters for the action to template fields from the event, e.g. `{"foo": "foo-value", "failed_flow_run": "{flow_run_id}"}`