{"version":"2.1.265","anchor":"workflow-run-ids-get-a-dedicated-format-and-telemetry-hashin","canonical_anchor":"workflow-run-ids-get-a-dedicated-format-and-telemetry-hashin","heading":"Workflow run IDs get a dedicated format and telemetry hashing path","tier":"internal","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/workflow-run-ids-get-a-dedicated-format-and-telemetry-hashin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Workflow run IDs get a dedicated format and telemetry hashing path\n\nWorkflow run IDs now use a dedicated ID format with their own telemetry hashing path\n\n**What**\n\nWorkflow run IDs now follow a specific recognizable shape (a `wf_` prefix followed by hex characters). Internally, IDs matching this shape are now hashed and redacted differently from other custom identifiers before being included in telemetry data.\n\n**Why**\n\nThis is an internal bookkeeping change affecting how workflow run identifiers are anonymized before being sent in telemetry; it doesn't change what you see or do when using workflows.\n\n- Area: Workflows\n- Names: `wf_`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}