{"version":"2.1.246","anchor":"error-messages-are-trimmed-much-harder-before-being-reported","canonical_anchor":"error-messages-are-trimmed-much-harder-before-being-reported","heading":"Error messages are trimmed much harder before being reported","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/error-messages-are-trimmed-much-harder-before-being-reported","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Error messages are trimmed much harder before being reported\n\nError text sent for diagnostics is now cut down much more aggressively before it leaves.\n\n**What**\n\nErrors sent for diagnostics now have far more removed from them: failed process launches are cut off at the error code, command failure, timeout and cancellation messages are truncated, anything after `Executable not found in $PATH: ` is dropped, and allowed\/blocked domain messages are trimmed generally.\n\n**Details**\n\n- The launch-failure list now covers the full set of system error codes from `EACCES` through `EXFULL`, plus `UNKNOWN` and \"Unknown system error\".\n- AWS resource identifiers are no longer blanked wholesale: a structured replacer keeps the partition, service and region while removing the rest, and a second pattern covers wildcarded policy identifiers.\n\n**Evidence**\n\n`Executable not found in $PATH: `\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}