Hi, honestly I’m not sure if it’s prefect related, but, when I try to run the graphql query to turn off a specific flow:

mutation {
  set_schedule_inactive(input: {flow_id: "67d364da-375d-4d0f-b151-d46435351c50"}) {
    success
  }
}

I get:

"message": "field \"set_schedule_active\" not found in type: 'mutation_root'"

I’m basically trying to use the query from the documentation here

@Bruno Kuasney I’ve just tried it and it seems to work, see image. 1. What is your Server version? Is your Server version >= Prefect version on your flow? 2. How do you call it - from Python or UI? Could it be something related to expired session or invalid API key? Btw in your query you have set_schedule_inactive and in your error message there is “set_schedule_active not found” 😄 something is funny here. Can you refresh your browser and try the query again? Also, make sure the flow ID is correct

yeah, regarding the “funny thing” is just a copy and paste problem xD but both functions are not working. I’m using the UI just to validate, to then try to use on python. Gonna check this “version” problem. Thx 🙂

Can you try running it in the GraphQL playground in the Prefect Server UI? http://localhost:4200/graphql

did it run on this place, but I’m not sure what this place does

did it work? Can you see success? The above link is the GraphQL API playground automatically included in your Prefect Server installation. It’s already authenticated and therefore you can use it directly from your Prefect UI

I mean, “success” is false, but at least is not an error (honestly is first time playing around graphql), so probably this mean is not working as well =S

can you share some screenshots? can you see the scheduled being toggled off now?

here is the query and the result

@Bruno Kuasney could it be that the flow_id is outdated? I see that you use the Version 2, perhaps you have an ID of Version 1?

srry for the delay, ok, how can I get (or check) this? to get this id I just ran

query {flow(where:{project: {name: {_eq: "Protect"}}, archived: {_eq: false}}) {id}}

yes, exactly, you can query first for your unarchived flow to get the ID, and then pass it to the next one. But you can also set the schedule active or inactive during registration:

flow.register(set_schedule_active=False)

hmmm that’s a good one! thx a lot @Anna Geller for the help 🙂