{"version":"2.1.274","anchor":"artifact-create-call-now-threads-an-explicit-requestid","canonical_anchor":"artifact-create-call-now-threads-an-explicit-requestid","heading":"Artifact create call now threads an explicit requestId","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/artifact-create-call-now-threads-an-explicit-requestid","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Artifact create call now threads an explicit requestId\n\nArtifact creation calls now can carry an explicit requestId\n\n**What**\n\nThe function that creates a new artifact now accepts an additional parameter and, when it's set, forwards it as `requestId` in the request sent to create the artifact.\n\n**Why**\n\nThis is internal plumbing that lets an artifact-creation request be tagged with a specific request identifier; it has no direct visible effect on how artifacts are created.\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}