Hey, I have a flow that is triggered by an API call from an external process. Sometimes, the process fails, and the API call doesn’t send, meaning the flow is not triggered. Is there a way to monitor those delays? I mean - If the flow doesn’t triggered by 8 am, is there a way to monitor it and send a Slack notification or an email? Thanks. @Taylor Curran

Hi @Noam Banay, great question! We definitely want to support that pattern, and this is something we are actively working on as part of the Observability feature that will allow you to configure custom SLA exactly as you described.

Thanks @Anna Geller! We are using Rivery as part of our pipeline. Each process (or ‘river’) update a table in our data warehouse (BQ). Those tables are in use in different ETLs queries. So after a river is completed successfully , a REST API call is send to trigger the relevant flow that trigger a DBT job.

in that case, you could solve it by leveraging dbt freshness check -- this would check if the BQ table was updated and only then trigger the dbt run https://docs.getdbt.com/reference/resource-properties/freshness you could error if not fresh and use Prefect flow or task-level retries to retry this run until the freshness check passes (not saying it's an ideal solution, but it would be a pragmatic poor man's SLA)