{"version":"2.1.234","anchor":"out-of-order-artifact-share-checks-are-merged-not-thrown-awa","canonical_anchor":"out-of-order-artifact-share-checks-are-merged-not-thrown-awa","heading":"Out-of-order artifact share checks are merged, not thrown away","tier":"notice","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/out-of-order-artifact-share-checks-are-merged-not-thrown-awa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### Out-of-order artifact share checks are merged, not thrown away\n\nArtifact sharing status no longer shows stale info when two checks overlap.\n\n**What**\n\nWhen two checks of an artifact's share status overlapped, the one that landed out of order was discarded, which could leave a stale sharing state on screen. Results are now merged.\n\n**Details**\n\n- Both the time a check was issued and the time it landed are tracked, and each result is classified as older-issued, overlapped, or current.\n- Merging takes the more restrictive share mode, ORs the live-share flag, preserves a prior check failure, and keeps the later of the two issue timestamps.\n- A failed check now records its landing time too, so a later overlapping success merges correctly.\n\n**Evidence**\n\n`probeFailed`\n\n- Area: Artifacts\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}