Decision: Heartbeats Enabled but No Default Tasks

Status: Decided
Channel: #x-all
Participants: Vishal Joshi, DK, Madhur Joshi

Context

Part of the Client #2 onboarding readiness discussion. The team debated whether heartbeats (scheduled/recurring tasks) should be enabled by default.

The Debate

• DK's position: Heartbeats shouldn't be enabled by default on day 1 — "people wouldn't love it day 1, especially when it's actively charging them"
• Madhur's position: The capability should be enabled — "of course the customer will decide what they want to run. But the capability should be enabled"

Decision

Heartbeat capability is enabled by default. Default heartbeat tasks are removed.

The scheduler infrastructure is present and active, but no tasks run until the customer explicitly configures their own. This means:

• The feature is discoverable and available from day 1
• No unexpected charges from tasks the customer didn't ask for
• Customers have full control over what runs and when