Hi folks, I am getting an INTERVAL_SERVER_ERROR trying to enable heartbeat using a graphql mutation query to prefect cloud

Hi @Marwan Sarieddine - to be precise, what graphql call are you making?

query:

mutation {
            enable_flow_heartbeat(input: { flow_id: "$flow_id" }) {
                success
            }
        }

traceback

File "/Users/marwansarieddine/.pyenv/versions/etl-embs/lib/python3.8/site-packages/infima/toolkit/prefect/runner.py", line 174, in _toggle_heartbeat
    return _toggle_flow_option(client=client, flow_id=flow_id, action=action)
  File "/Users/marwansarieddine/.pyenv/versions/etl-embs/lib/python3.8/site-packages/infima/toolkit/prefect/runner.py", line 169, in _toggle_flow_option
    client.graphql(query=query)
  File "/Users/marwansarieddine/.pyenv/versions/etl-embs/lib/python3.8/site-packages/prefect/client/client.py", line 294, in graphql
    raise ClientError(result["errors"])
prefect.utilities.exceptions.ClientError: [{'path': ['enable_flow_heartbeat'], 'message': '"\'Box\' object has no attribute \'enable_heartbeat_for_flow\'"', 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}]

ok interesting, this definitely looks like a bug on our side

disable_flow_heartbeat

seems to be working fine on the other hand ...

mutation {
            disable_flow_heartbeat(input: { flow_id: "$flow_id" }) {
                success
            }
        }

AH! We recently did an internal refactor of the API for flow settings and it appears you found a route that wasn’t correctly updated. I can prioritize this and we should be able to release it fairly quickly (on the order of 1-2 days)

I see - thanks for looking into this, it is not mission critical from our end given there are other ways to enable heartbeat ... but it would be nice to have it fixed 🙂

yup we’ll definitely get it fixed 👍 I’ll report back when it’s queued up for release

sounds good - thank you!

Hi @Marwan Sarieddine - the fix has been released, you should be able to re-enable heartbeats for your flows now! Thanks for bringing this to our attention

Hi @Chris White - thank you for the update 🙂