Use a queryable error event API plus a separate schedule monitor when a Node.js SaaS marketplace needs alerting for imports that stop producing results. The decision rule is strict: advance an import watermark only after the result is durable, and make alert delivery retryable without letting notification state rewrite that watermark. A thrown error is evidence of one failure; missing expected output is evidence that the workflow itself may have stopped.
TL;DR: emit structured start and terminal events from the Node.js worker, store them behind a small query API, and run an independent cron monitor that compares each schedule's deadline with its last successful result. Send Slack or email through an idempotent outbox.…