hey Prefect! I have disabled heartbeat and Lazarus for one of my flow using UI, however it seems that prefect is still retrying the flow. I am seeing 2 log messages which matches

Beginning Flow run for '….'

which indicates that flow was retried by prefect. Any ideas? It seems that heartbeat is also not disabled, as we are seeing logs

No heartbeat detected from the remote task; marking the run as failed.

FYI we are using prefect server community Core Version 1.2.0+10.gafda99411

This page explains the problem and gives some suggestions on how you can approach it https://discourse.prefect.io/t/flow-is-failing-with-an-error-message-no-heartbeat-detected-from-the-remote-task/79

@Anna Geller I am already trying the suggested approach. The problem is still happening after disabling the heartbeat. It seems that prefect is ignored the disabled heartbeat setting and sending the heartbeats anyway

I totally understand your pain, but we don't have a robust solution for this atm - we'll work on improving that UX in 2.0

when I check the flow using graphql query. flow_group_by_pk for the specific flow_group_id, the config is as expected, as per UI toggles

"lazarus_enabled": false,
        "disable_heartbeat": true,
        "heartbeat_enabled": false,

It seems the prefect’s heartbeat and lazarus service is not respecting these config items

Gotcha. if you want to, you can open a GitHub issue in the Server repo and describe the issue in more detail there. It will get better in 2.0 🤞