A useful error path preserves enough information to correct the problem. Keep the entered draft when a source write fails, show the relevant form error and avoid navigating to a success screen. A fallback that hides every failure can make the app appear healthy while losing the requested work.
Different causes need different responses. A read-only source, a one-time connector failure and a concurrency conflict do not have the same recovery. Gather the app version, environment, record identity and operation alongside the exact error and source outcome. Exclude secrets and unnecessary personal data. These tasks pair checked local failures with an individual diagnostic handoff rather than treating a screenshot as a complete cause.