From 224846d564f6bfc58750e1bf50b12e7fcad33977 Mon Sep 17 00:00:00 2001 From: josebarrueta Date: Fri, 28 Aug 2026 13:07:27 -0700 Subject: [PATCH] docs(tool-executions): say why this page calls two different hosts MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The page reads history from one host and writes policy to another, thirty lines apart, with nothing saying why. Both are right — history is served by the Engine, the organization's settings by the control plane — but a reader who notices the difference has no way to tell it from a typo, and guessing wrong costs them a 404 on a path that looks correct. Named once, where the first host appears, with the path prefixes attached because they differ together. Co-Authored-By: Claude Opus 5 --- app/en/operate/governance/tool-executions/page.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/app/en/operate/governance/tool-executions/page.mdx b/app/en/operate/governance/tool-executions/page.mdx index 2443bc6d0..3eee8c8b9 100644 --- a/app/en/operate/governance/tool-executions/page.mdx +++ b/app/en/operate/governance/tool-executions/page.mdx @@ -111,6 +111,8 @@ Two consequences are worth knowing. The same history is available over the Arcade API. The base URL is `https://api.arcade.dev`, and requests authenticate with a bearer token. +Reading history and changing the policy are two different services, so they answer on two different hosts. Execution history is served by the Engine at `https://api.arcade.dev`; the recording and retention settings below belong to your organization and are served by the control plane at `https://cloud.arcade.dev`, alongside the [audit log API](/operate/governance/audit-logs). The host and the path prefix differ together — `/v1/...` on the Engine, `/api/v1/...` on the control plane. + List the runs that failed, 25 at a time: ```bash