Safe Production Error Exposure Sanitized client responses, protected diagnostics, logging hygiene, and privacy-aware failure handling
Phase 13 - Professional Error Handling Volume 04 - Professional Backend
Architecture milestone client-safe response
↓
requestId
↓
private structured diagnostic log
Phase 13 creates one professional exception boundary and a correlation story that spans client response and server logs.
Production errors should be boring to clients and rich to engineers The client needs a safe message, stable code, and requestId. Engineers need internal context such as exception name, stack, method, path, status, and timing. These are different audiences.
status / code Yes Yes
human-safe message Yes Yes
requestId Yes Yes
stack trace No Yes for unexpected faults
raw SQL No Usually no; only under controlled diagnostics
request password/token Never Never
Structured logging example this.logger.error("Unhandled request failure", { requestId, method: request.method, path, statusCode: 500, exceptionName: exception.name, stack: exception.stack, });
Do not log request bodies by default Bodies can contain passwords, tokens, personal data, payroll values, applicant information, employee records, or uploaded document metadata in future TaskFlow-derived systems. Logging everything because it is convenient is not professional observability.
Error handling is also data-handling design. Decide what logs are allowed to contain before production, who can read them, and how long they are retained.
Unknown 500 workflow Figure 1 - Safe 500 lifecycle Unexpected exception occurs
↓
↓
↓
↓
A secure system does not need to choose between debuggability and safe client responses.
Deployment is the controlled movement of a versioned artifact into a configured runtime with evidence of health and a credible rollback path.
Restate the goal of “Safe Production Error Exposure” as one observable behavior. Write the success signal before touching code.
Trace the boundary map: versioned artifact → production config → runtime → health/smoke test → rollback path. Mark the one boundary this lesson changes.
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
Connect the slice to TaskFlow’s phase artifact: Error taxonomy + NestJS mapping layer/filters + structured error response with request IDs.. Verify behavior from the outside as a user or API client would.
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.
1. Build an immutable artifact.
2. Apply production configuration/secrets.
3. Run compatible migrations.
4. Start the new version.
5. Check readiness and smoke tests.
6. Observe errors/latency.
7. Promote or execute rollback.Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.
Separate platform deploy status from application readiness; run smoke tests against real routes and dependencies.
Use expand/contract migrations and keep rollback compatibility explicit before release.
Without copying the final source, create a second small scenario that applies “Safe Production Error Exposure” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.
Create explicit application errors for expected business outcomes rather than throwing arbitrary strings.
Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.Logging secrets/tokens with error context
Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?
If your explanation is vague, repeat the boundary trace before moving on.Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.