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

we've recently been seeing StartFlowRun create multiple runs with the same `idempotency_key` &lt;24 hours apart (say 30 mins). is the idempotency key queryable from graphql so we could try to debug what's going on?

Hi <@UL455076D> - you should be able to get idemp keys directly on the flow_run object:
```query {
  flow_run {
    id
    idempotency_key
  }
}```

perfect, thanks! but also....how..?
```{
  "data": {
    "flow_run": [
      {
        "id": "c49cbc75-61d9-4aaf-b857-18ee1890b4cd",
        "idempotency_key": "99a33702-9dcf-4e77-aa1f-c42474b8375c",
        "created": "2021-06-09T19:31:12.624111+00:00"
      },
      {
        "id": "0af54c93-fdd3-4010-85bd-c01437cc2423",
        "idempotency_key": "99a33702-9dcf-4e77-aa1f-c42474b8375c",
        "created": "2021-06-09T19:58:21.764191+00:00"
      }
    ]
  }
}```

Hm, do the parameters change between those runs?

nope, in fact it's created by a worker dying and then the exact same parent task re-running. so there's really no way there could be anything different about the runs

Hm let me elevate this, I don't have any immediate thoughts then

<@UL455076D> for the runs you posted, the containing flow ids are different for those runs - it looks like the flow was re-registered between those calls

ahhh ok, I guess the actual task must be doing something like "register-and-run" so when it re-runs they both happen. thanks for the explanation!