From c3e87e2f67720e70d17f067e54c4d74c8610b633 Mon Sep 17 00:00:00 2001 From: Richard McDaniel <1130888+rmcdaniel@users.noreply.github.com> Date: Fri, 13 Nov 2026 00:26:47 +0000 Subject: [PATCH] Say the Server does not send invocable_http requests (#527) Native validates invocable_http mappings and returns them on activity polls but has no HTTP client. The server reference now says a process you run must poll, call the endpoint and report the result, and that with no poller the task waits. General's decision on #527: correct the docs now, build a dispatcher on demand. Co-Authored-By: Claude Opus 5.5 --- docs/server-reference.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/server-reference.md b/docs/server-reference.md index d2c6e8243..2c114bdee 100644 --- a/docs/server-reference.md +++ b/docs/server-reference.md @@ -1062,7 +1062,12 @@ capabilities, before mapping it onto pollable activity tasks. The carrier must also resolve an `auth_ref` for non-loopback targets; only loopback HTTP development targets may omit auth. Effective auth remains redacted in cluster diagnostics and activity poll responses. -retry policy is transport-only: it may repeat transient HTTP delivery before a +The Server never sends the HTTP request itself. A process you run must poll +the activity queue, read `task.external_executor`, call the endpoint and +report the result through the normal complete/fail paths. If nothing polls +the queue, the activity task waits. A Server-side dispatcher will be built +when users need it (#527). +The carrier retry policy is transport-only: it may repeat transient HTTP delivery before a result is reported, while durable activity retry remains owned by the server/runtime after complete/fail reporting. For leased invocable mappings, `task.external_executor.dispatch` also exposes