Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

I have a flow that appears to be running and then it fails with this message, however, I don't think it is failing.
```No heartbeat detected from the remote task; marking the run as failed.```

Hi <@U016PHZHN8Z>!

This is happening because Prefect Cloud is expecting the Flow to update its heartbeat every 30 seconds. When it missing 4 heartbeats, Cloud decides that something has happened to the flow

Double-check to make sure your Flow can communicate with Cloud in its current environment

It will need to be able to make calls to `<http://api.prefect.io|api.prefect.io>`.

If other updates are getting to Cloud (logs, state updates, etc) and you believe the flow is working as expected, you can turn heartbeats off via the flow settings in the UI

I am currently running server on local, I am still waiting for our Enterprise Cloud server.

The same architecture pattern is in place for server :thumbsup:

Can your flow communicate with your Prefect Server instance?

<@UKVFX6N3B> looks like it is communicating with the server, unless the flow finishes and then it still thinks it is running, where do I find the flow settings?

Or does the flow enter a running state and then stall out?

<https://docs.prefect.io/orchestration/ui/flow.html#settings>

You’ll need to issue a graphql statement: <https://docs.prefect.io/orchestration/concepts/flows.html#toggling-heartbeats>

<@UKVFX6N3B> thanks, I will look into this one.