Short answer: the best practices for handling uncaught exceptions in Node.js error tracking are to install one global last-resort handler, capture a small structured event, stop accepting new work, and let the scheduler retry the import. The handler is a safety boundary, not a recovery mechanism. For a marketplace import, the useful question is not only whether an exception was recorded; it is whether an operator can decide what to replay without creating duplicate ledger entries.

A scheduled import has a particularly awkward failure shape. It can die after fetching a page, after writing a product, or after committing a batch while its own process still has time to emit a final log line. Treating every uncaught exception as a normal application error hides that distinction. Treating it as a reason to keep serving requests is worse.

The design below keeps the event useful, the shutdown bounded, and the retained data proportional to the reconstruction job.…