Add `in_process_retries` and `reschedule_retries` fields to `FlowRunPolicy`

[kevingrismore]

Describe the current behavior

The FlowRunPolicy model currently has a retries field that tracks how many retries have occurred on a flow run.

Describe the proposed behavior

We should add in_process_retries and reschedule_retries fields so that it's easy to track how many of each type of retries have occurred.

Example Use

No response

Additional context

This information will help us provide great and precise clarity on the flow run page!

[harsh21234i]

Hi @kevingrismore, this looks like a really useful improvement

From what I understand, the current retries field mixes different retry types together, so splitting it into in_process_retries and reschedule_retries would make things much clearer, especially when debugging flow runs.

I’d be interested in working on this. Before I start, just wanted to clarify a couple of things:

• Where is the main place in the code where retries are updated, so I can correctly separate the two types?
• Should the existing retries field still be kept as a total, or should it be derived from the new fields?

Happy to take this on once I have a bit more clarity. Thanks!