Short answer: use one Express error-tracking middleware setup that emits a normalized JSON event with run_id , property_id , stage , and error_code ; retain the compact event longer than its raw payload so nightly property-pipeline costs can be attributed without storing every request body.
A nightly property-management pipeline usually does not need a bigger error platform. It needs one error record that answers three questions: which run failed, which property or tenant cohort was affected, and what retention decision created the bill. Put that context into structured logs at the Express boundary, propagate a request or job identifier, and keep verbose payloads on a short retention schedule.
The least complex useful implementation is an error-handling middleware that emits one normalized event per failed request, while the pipeline worker emits the same shape for scheduled jobs.…