{"version":"2.1.273","anchor":"artifact-call-endpoint-action-gets-its-own-working-directo","canonical_anchor":"artifact-call-endpoint-action-gets-its-own-working-directo","heading":"Artifact 'call_endpoint' action gets its own working-directory resolution via body_file","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/artifact-call-endpoint-action-gets-its-own-working-directo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### Artifact 'call_endpoint' action gets its own working-directory resolution via body_file\n\nThe artifact tool's call_endpoint action now figures out its working directory from body_file instead of file_path\n\n**What**\n\nWhen the artifact tool runs a `call_endpoint` action, it now determines the working directory from a `body_file` field, rather than from `file_path` as other artifact actions do.\n\n**Why**\n\nThis is a targeted fix so `call_endpoint` resolves its working directory from the field that's actually relevant to it, rather than one meant for other action types.\n\n- Area: Artifacts\n- Names: `body_file`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}