Heartbeat monitoring for Go import jobs: alert on missing completions, not just dead processes

A marketplace import page should trigger when scheduled imports stop producing results, rather than only when the API process crashes. The recommended approach is an external heartbeat monitor, such as Healthchecks or Better Stack, to detect a missing completion, with errors, logs, and metrics used to explain the cause. Alerts should name the late import, its last successful completion time, and how far it is past its expected interval. The runbook then checks in order whether a run started, whether it failed, and whether it produced a plausible result count, which keeps rollback decisions safe. The article also suggests sending a success heartbeat only after results are committed, with thresholds set from the schedule plus normal runtime and a grace period.