Jingjing Duan

@ohaibbq thanks for tracking down the problem and fixing it as well! I'll let you know if I still see this issue.

@int128 can you take a look? Our workflow keeps getting larger and larger. It would be great if this action can send all the metrics of a workflow run, even...

What I see often is that a run was successfully triggered (the "Distinct ID" matches the expected ID) but this action couldn't find it after many tries.

Good idea. I just added that secret. Will keep you posted. Thanks!

So this happened today. It failed to find a workflow run with the matching dispatch id:  However, the workflow run was dispatched successfully (the id matches) 

The action was dispatched at `Thu, 14 Sep 2023 04:44:27 GMT` and the job started running at `Thu, 14 Sep 2023 04:44:35 GMT` so it took 8 seconds. We use...

Sorry what you mean exactly?

No, that job only has one step like this: ``` id: runs-on: [infra, us-central1, build-small] if: ${{ github.event.inputs.distinct_id != null }} steps: - name: Distinct ID ${{ github.event.inputs.distinct_id }} run:...

@pmrotule that's great insight. It's certainly possible that the target workflow has more than 5 concurrent runs at some point. It'd be great to make this a configurable param! @Codex-

@Codex- can you given a summary of the recent enhancements? We do use `v1` across the board so we will pick up the enhancements automatically.