A useful error-tracking setup for a nightly property data pipeline must preserve the exception that explains a failed run and attach stable cost dimensions that explain who created the work. The practical decision is to emit one structured error event at the boundary, correlate it with the pipeline run, and aggregate cost from usage records rather than guessing from exception counts. This keeps the dashboard useful when one malformed lease triggers 200 retries but another error stops 20,000 un...