<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Human-in-the-Loop-Patterns on Agent Zone</title><link>https://agent-zone.ai/skills/human-in-the-loop-patterns/</link><description>Recent content in Human-in-the-Loop-Patterns on Agent Zone</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 22 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://agent-zone.ai/skills/human-in-the-loop-patterns/index.xml" rel="self" type="application/rss+xml"/><item><title>Temporal Signals: Human-in-the-Loop and Manual Approval Workflows</title><link>https://agent-zone.ai/knowledge/workflow-orchestration/temporal-signals-manual/</link><pubDate>Sun, 22 Feb 2026 00:00:00 +0000</pubDate><guid>https://agent-zone.ai/knowledge/workflow-orchestration/temporal-signals-manual/</guid><description>&lt;h1 id="temporal-signals"&gt;Temporal Signals&lt;a class="anchor" href="#temporal-signals"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Workflows often need input after they have started. A deployment workflow pauses for human approval. An expense workflow waits for a manager&amp;rsquo;s signature. An incident response workflow escalates after a timeout. Temporal signals are the mechanism for delivering external input to a running workflow.&lt;/p&gt;
&lt;p&gt;A signal is a message sent to a workflow from outside &amp;ndash; from another workflow, from a CLI command, from an HTTP endpoint, or from any system that has the Temporal client. The workflow receives the signal, processes it, and continues execution. Signals are durable: if the worker crashes after a signal is sent but before the workflow processes it, the signal is replayed when the worker restarts.&lt;/p&gt;</description></item></channel></rss>