https://prefect.io logo
Title
r

Richard Hughes

08/20/2020, 2:14 PM
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.
d

Dylan

08/20/2020, 2:16 PM
Hi @Richard Hughes! 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
r

Richard Hughes

08/20/2020, 2:18 PM
I am currently running server on local, I am still waiting for our Enterprise Cloud server.
d

Dylan

08/20/2020, 2:21 PM
The same architecture pattern is in place for server 👍
Can your flow communicate with your Prefect Server instance?
r

Richard Hughes

08/20/2020, 2:32 PM
@Dylan 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?
d

Dylan

08/20/2020, 2:37 PM
Do you get any task run updates?
Or logs from running task runs?
Or does the flow enter a running state and then stall out?
Ah it’s cloud-only, my mistake
r

Richard Hughes

08/20/2020, 3:33 PM
@Dylan thanks, I will look into this one.
d

Dylan

08/20/2020, 3:38 PM
👍