Hi, just wondering if there is a way to clear the idempotency key cache through graphql? We are evaluating Prefect and testing flow runs from a different backend service, but if our hash matches a run that failed, it will just return that run ID instead of creating a new run. So it would be great if we could pass a flag to first clear the cache and then create the flow run during testing.

Hey @Brad I -- are you using Prefect Server or Cloud?

Sorry, we’re using cloud

I do not think we provide a way to clear idempotency keys without direct access to the database, they're a unique constraint at the database level. You can delete the flow run entirely using the

delete_flow_run

mutation which should solve your problem

ok, will give that a try, thanks!