Machine doesn't get deactivated with dead heartbeat

[FuRi0n]

I'm having some problems with the heartbeat. I have a policy with heartbeats enabled, if a machine is activated but it never sends his first heartbeat it never gets deactivated, taking a slot on the license. If the machine manages to send his first heartbeat everything works correctly. Is there a way to make these dead machines to deactivate automatically?

[ezekg]

Hey @FuRi0n, if you enable requireHeartbeat on the policy, the machine will automatically start its heartbeat after it is activated. So if it fails to send another heartbeat within the allotted window, it will be deactivated. If requireHeartbeat is not set, then the machine will never be considered dead, since it never started its heartbeat monitor.

This should resolve the issue you're seeing.

[FuRi0n]

Hi, doesn't look like that works, this is the policy I'm using:

And this is my machine configuration:

As you can see the policy is configured with 2 minutes heartbeat and 1 minute resurrection period. The machine has been dead for over 4 minutes and it's still there, it never gets deleted unless I sent the first heartbeat, then it gets deleted correctly after 3 minutes.

[ezekg]

Can you please email support so that I can get more information on this machine, such as ID and account ID? It may take a few minutes for a machine to automatically be pruned after it has died.

[email protected]