---
title: "Durable Recipes"
description: "What Tooluse.net Recipes guarantee and where their private runtime boundary begins."
---

> Documentation Index
> Fetch the complete documentation index at: https://help.tooluse.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Durable Recipes

<p>A Recipe is persisted automation dispatched to a deterministic native execution. Tooluse.net’s workflow engine remains the scheduler and execution owner; the private Recipe runtime maintains domain state and receipts.</p>
<h2 id="why-recipes-are-separate">Why Recipes are separate</h2>
<p>Workflow YAML describes execution. Recipe state describes the durable automation product behavior around that execution. Keeping the two separate prevents an internal scheduler or queue from creating a second source of truth.</p>
<h2 id="boundaries">Boundaries</h2>
<ul>
<li><code>/v1/internal/recipes/dispatch</code> and <code>/v1/internal/recipes/runtime</code> are private bridges, not developer endpoints.</li>
<li>A Recipe does not bypass application authorization, service connection limits, idempotency, or human approval.</li>
<li>The presence of a retained adapter does not make an unfinished channel or transport public.</li>
</ul>
<h2 id="see-also">See also</h2>
<ul>
<li><a href="/automation/workflows">Deploy and publish a workflow</a></li>
<li><a href="/reference/private-endpoints">Private and callback endpoints</a></li>
</ul>

Source: https://help.tooluse.net/automation/recipes/index.mdx