This is stopping the pod from starting because the CPU request, fargate cannot provision it. But the original flow run ran fine until we ran into an error, and now I need to restart it

i’m trying to restart but for some reason when its spinning up the new pod its requesting CPU that the original run config did not set.

Restarts normally don't create a new flow run, instead they update task run history for failed task. So if your Kubernetes pod defined for this flow run is no longer around, Prefect probably does it best to infer that using the default configuration set on the agent, that's why you probably see the same config that is used by default when you don't specify any custom CPU request on your

KubernetesRun

now I need to restart it

This is tricky for the reasons I mentioned above. Maybe you can temporarily comment out the tasks you don't wanna run, register your flow, trigger your flow run with the task that you need to rerun (2 CLI commands will do) then you can uncomment and reregister the flow - that's probably the fastest way alternatively, with Prefect you can always (re)run your flow locally so that's also an option

Hmm, how do i update the default agent - because I did define a kubernetes run cpu request I think

in the run config, as shown above

and it works normally