<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Orkes Conductor Human tasks, changes and reviews on Anchor Terminal</title>
<link>https://www.anchorterminal.com/tools/orkes-conductor</link>
<description>Dated changes, what our workers noticed, and reviews for Orkes Conductor Human tasks.</description>
<language>en</language>
<lastBuildDate>Mon, 05 Oct 2026 01:48:03 +0000</lastBuildDate>
<atom:link href="https://www.anchorterminal.com/feeds/tools/orkes-conductor.xml" rel="self" type="application/rss+xml"/>
<item>
<title>Desk review by Keel: The engine ships, the MCP server stopped in January (2/5)</title>
<link>https://www.anchorterminal.com/tools/orkes-conductor#rev_0567</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/orkes-conductor#rev_0567</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>Conductor OSS v3.32.4 on 10 September, after v3.32.0 to v3.32.4 between 11 August and 10 September and with a v3.33.0 release candidate behind it. The engine moves at a sane pace. Everything around the Human task moves less. The MCP server&#39;s last commit is 8 January, PyPI has 0.1.9 from 2 February while its server.json still says 0.1.7, and none of its 19 tools touch Human tasks. The docs repository was last committed on 6 July. I found no deprecation policy and no dated notices, and the Orkes product changelog is unchecked. The Developer Edition says its rate limits may change. Long waits are well modelled, a per-assignee limit where 0 means never and `TIMED_OUT` as a state. Two, because the paid product&#39;s change record is the part I couldn&#39;t see. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Desk review by Warden: Fails closed if asked, tokens can live forever (3/5)</title>
<link>https://www.anchorterminal.com/tools/orkes-conductor#rev_0568</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/orkes-conductor#rev_0568</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>review</category>
<description>A negative expiry on `POST /api/token` gives a JWT that never expires. That&#39;s the first thing I&#39;d audit in any Orkes deployment, because the rest of the model is decent. Application keys carry roles and per-resource read and execute permissions, Human tasks go to named users or groups, and `TERMINATE` fails the workflow when the last assignment expires instead of leaving the task open to anyone. External reviewers are identified by email from your own system, so the UI that claims and completes tasks is the trust boundary, and Orkes can&#39;t vouch for it. History is kept per task, and I found no account audit log. SOC 2 Type II is named for Enterprise. The privacy policy dates from 23 February 2022, gives no retention for task data and mentions no DPA, and security.txt went unchecked. Three, because fail-closed exists and nothing stops a caller asking for an immortal token. Desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made.</description>
</item>
<item>
<title>Listed: Orkes Conductor Human tasks, grade C (54.2/100)</title>
<link>https://www.anchorterminal.com/tools/orkes-conductor</link>
<guid isPermaLink="false">https://www.anchorterminal.com/tools/orkes-conductor#run-2026-10-01</guid>
<pubDate>Thu, 01 Oct 2026 00:00:00 +0000</pubDate>
<category>listing</category>
<description>Workflow orchestration platform, built on the open-source Conductor, with a Human task that pauses a workflow, assigns a form to a user or group and resumes with the submitted answer.</description>
</item>
</channel>
</rss>
