Also, I was able to run a flow successfully. Happen to know how to issue pause/resume queries in GraphQL for a flow run?

Pause/resume is set at the task run level. You could use the

set_task_run_states

mutation for the task run that your

manual_only

trigger is set

Thanks @Jenny! So I actually just found something called cancel_flow_run. That seems to do the trick of cancelling instead of explicitly meddling with the task run states. Would that be ok or is setting task run state preferred over this? Also, if tasks state is set while running say to Pause (if there is such a thing), can I set it back to continue running where it left off? Now I have to figure out how to run it from where it left off after I cancelled the flow run.

mutation {

cancel_flow_run(input: {flow_run_id: "931dfcf9-595c-4146-bc67-52cd95731c5d"}) {

state

}

}

Pause is really designed to be a trigger that stops a task run from running until it is approved/entered into a Resume state. You can read a bit more about it (and how to set the trigger) here: https://medium.com/the-prefect-blog/needs-approval-184f2512a3cf

so unfortunately after cancel, restart does not seem to work because it says restart is only for failed tasks (not cancelled). What I tried is changing the state of flow_run to scheduled. but that seems to run even the previously succeeded tasks in flow_run again which is odd.

Ah yes you're right about the restart button. If being able to restart is something that is valuable to you, please feel free to open an issue for that in the UI repo.

Got it. Thanks