@mastra/mcp-docs-server 0.13.22-alpha.1 → 0.13.22-alpha.3

package/.docs/raw/frameworks/agentic-uis/cedar-os.mdx

@@ -0,0 +1,108 @@
+---
+title: 'Cedar-OS Integration'
+description: 'Build AI-native frontends for your Mastra agents with Cedar-OS'
+---
+
+
+import { Tabs, Steps } from "nextra/components";
+
+# Integrate Cedar-OS with Mastra
+
+Cedar-OS is an open-source agentic UI framework designed specifically for building the most ambitious AI-native applications. We built Cedar with Mastra in mind.
+
+## Should you use Cedar?
+
+There are a few pillars we care about strongly that you can read more about [here](https://docs.cedarcopilot.com/introduction/philosophy):
+
+#### 1. Developer experience
+- **Every single component is downloaded shadcn-style** – You own all the code and can style it however you want
+- **Works out of the box** – Just drop in our chat component, and it'll work
+- **Fully extensible** - Built on a [Zustand store architecture](https://docs.cedarcopilot.com/introduction/architecture) that you can customize completely. Every single internal function can be overridden in one line.
+
+#### 2. Enabling truly AI-native applications
+For the first time in history, products can come to life. We want to help you build something with life.
+- **[Spells](https://docs.cedarcopilot.com/spells/spells#what-are-spells)** - Users can trigger AI from keyboard shortcuts, mouse events, text selection, and other components
+- **[State Diff Management](https://docs.cedarcopilot.com/state-diff/using-state-diff)** - Give users control over accepting/rejecting agent outputs 
+- **[Voice Integration](https://docs.cedarcopilot.com/voice/voice-integration)** - Let users control your app with their voice
+
+## Quick Start
+
+<Steps>
+### Set up your project
+
+Run Cedar's CLI command:
+``` bash
+npx cedar-os-cli plant-seed
+```
+
+If starting from scratch, select the **Mastra starter** template for a complete setup with both frontend and backend in a monorepo
+
+If you already have a Mastra backend, use the **blank frontend cedar repo** option instead.
+- This will give you the option to download components and download all dependencies for Cedar. We recommend at least downloading one of the chat components to get started. 
+
+### Wrap your app with CedarCopilot
+
+Wrap your application with the CedarCopilot provider to connect to your Mastra backend:
+
+```tsx
+import { CedarCopilot } from 'cedar-os';
+
+function App() {
+	return (
+		<CedarCopilot
+			llmProvider={{
+				provider: 'mastra',
+				baseURL: 'http://localhost:4111', // default dev port for Mastra
+				apiKey: process.env.NEXT_PUBLIC_MASTRA_API_KEY, // optional — only for backend auth
+			}}>
+			<YourApp />
+		</CedarCopilot>
+	);
+}
+```
+
+### Configure Mastra endpoints
+
+Configure your Mastra backend to work with Cedar by following the [Mastra Configuration Options](https://docs.cedarcopilot.com/agent-backend-connection/agent-backend-connection#mastra-configuration-options).
+
+[Register API routes](https://mastra.ai/en/examples/deployment/custom-api-route) in your Mastra server (or NextJS serverless routes if in a monorepo):
+
+```ts mastra/src/index.ts
+import { registerApiRoute } from '@mastra/core/server';
+
+// POST /chat
+// The chat's non-streaming default endpoint
+registerApiRoute('/chat', {
+	method: 'POST',
+	// …validate input w/ zod
+	handler: async (c) => {
+		/* your agent.generate() logic */
+	},
+});
+
+// POST /chat/stream (SSE)
+// The chat's streaming default endpoint
+registerApiRoute('/chat/stream', {
+	method: 'POST',
+	handler: async (c) => {
+		/* stream agent output in SSE format */
+	},
+});
+```
+
+### Add Cedar components
+
+Drop Cedar components into your frontend – see [Chat Overview](https://docs.cedarcopilot.com/chat/chat-overview).
+
+Your backend and frontend are now linked! You're ready to start building AI-native experiences with your Mastra agents.
+</Steps>
+
+
+## More information
+
+- Check out the [detailed Mastra integration guide](https://docs.cedarcopilot.com/agent-backend-connection/mastra#extending-mastra) for more configuration options (or for manual installation instructions if something goes wrong)
+- Explore Mastra-specific optimizations and features we've built
+  - **Seamless event streaming** - Automatic rendering of [Mastra streamed events](https://docs.cedarcopilot.com/chat/custom-message-rendering#mastra-event-renderer)
+  - **Voice endpoint support** - Built-in [voice backend integration](https://docs.cedarcopilot.com/voice/agentic-backend#endpoint-configuration)
+  - **End-to-End type safety** - [Types](https://docs.cedarcopilot.com/type-safety/typing-agent-requests) for communicating between your app and Mastra backend
+- [Join our Discord!](https://discord.gg/4AWawRjNdZ) We're excited to have you :)

package/.docs/raw/getting-started/installation.mdx

@@ -12,7 +12,6 @@ To get started with Mastra, you’ll need access to a large language model (LLM)
 
 Mastra also supports other LLM providers. For a full list of supported models and setup instructions, see [Model Providers](/docs/getting-started/model-providers).
 
-
 ## Prerequisites
 
 - Node.js `v20.0` or higher

package/.docs/raw/memory/overview.mdx

@@ -26,7 +26,7 @@ All memory types are [thread-scoped](./working-memory.mdx#thread-scoped-memory-d
 
 ### Working memory
 
-Stores persistent user-specific details such as names, preferences, goals, and other structured data. Uses [Markdown templates](./working-memory-template.mdx) or [Zod schemas](./working-memory-schema.mdx) to define structure.
+Stores persistent user-specific details such as names, preferences, goals, and other structured data. Uses [Markdown templates](./working-memory.mdx) or [Zod schemas](./working-memory.mdx#structured-working-memory) to define structure.
 
 ### Conversation history
 

package/.docs/raw/reference/agents/ChunkType.mdx

@@ -5,7 +5,7 @@ description: "Documentation for the ChunkType type used in Mastra streaming resp
 
 import { Callout } from "nextra/components";
 import { PropertiesTable } from "@/components/properties-table";
- 
+
 # ChunkType
 
 <Callout type="warning">
@@ -826,24 +826,24 @@ for await (const chunk of stream.fullStream) {
     case 'text-delta':
       console.log('Text:', chunk.payload.text);
       break;
-    
+
     case 'tool-call':
       console.log('Calling tool:', chunk.payload.toolName);
       break;
-    
+
     case 'tool-result':
       console.log('Tool result:', chunk.payload.result);
       break;
-    
+
     case 'reasoning-delta':
       console.log('Reasoning:', chunk.payload.text);
       break;
-    
+
     case 'finish':
       console.log('Finished:', chunk.payload.stepResult.reason);
       console.log('Usage:', chunk.payload.output.usage);
       break;
-    
+
     case 'error':
       console.error('Error:', chunk.payload.error);
       break;
@@ -853,5 +853,5 @@ for await (const chunk of stream.fullStream) {
 
 ## Related Types
 
-- [MastraModelOutput](/reference/agents/MastraModelOutput) - The stream object that emits these chunks
-- [Agent.streamVNext()](/reference/agents/streamVNext) - Method that returns streams emitting these chunks
+- [MastraModelOutput](./MastraModelOutput.mdx) - The stream object that emits these chunks
+- [Agent.streamVNext()](./streamVNext.mdx) - Method that returns streams emitting these chunks

package/.docs/raw/reference/auth/firebase.mdx

@@ -0,0 +1,128 @@
+---
+title: "MastraAuthFirebase Class"
+description: "API reference for the MastraAuthFirebase class, which authenticates Mastra applications using Firebase Authentication."
+---
+
+# MastraAuthFirebase Class
+
+The `MastraAuthFirebase` class provides authentication for Mastra using Firebase Authentication. It verifies incoming requests using Firebase ID tokens and integrates with the Mastra server using the `experimental_auth` option.
+
+## Usage examples
+
+### Basic usage with environment variables
+
+```typescript filename="src/mastra/index.ts" showLineNumbers copy
+import { Mastra } from "@mastra/core/mastra";
+import { MastraAuthFirebase } from '@mastra/auth-firebase';
+
+// Automatically uses FIREBASE_SERVICE_ACCOUNT and FIRESTORE_DATABASE_ID env vars
+export const mastra = new Mastra({
+  // ..
+  server: {
+    experimental_auth: new MastraAuthFirebase(),
+  },
+});
+```
+
+### Custom configuration
+
+```typescript filename="src/mastra/index.ts" showLineNumbers copy
+import { Mastra } from "@mastra/core/mastra";
+import { MastraAuthFirebase } from '@mastra/auth-firebase';
+
+export const mastra = new Mastra({
+  // ..
+  server: {
+    experimental_auth: new MastraAuthFirebase({
+      serviceAccount: "/path/to/service-account-key.json",
+      databaseId: "your-database-id"
+    }),
+  },
+});
+```
+
+## Constructor parameters
+
+<PropertiesTable
+  content={[
+    {
+      name: "serviceAccount",
+      type: "string",
+      description: "Path to the Firebase service account JSON file. This file contains the credentials needed to verify Firebase ID tokens on the server side.",
+      isOptional: true,
+      defaultValue: "process.env.FIREBASE_SERVICE_ACCOUNT"
+    },
+    {
+      name: "databaseId",
+      type: "string",
+      description: "The Firestore database ID to use. Typically '(default)' for the default database.",
+      isOptional: true,
+      defaultValue: "process.env.FIRESTORE_DATABASE_ID || process.env.FIREBASE_DATABASE_ID"
+    },
+    {
+      name: "name",
+      type: "string",
+      description: "Custom name for the auth provider instance.",
+      isOptional: true,
+      defaultValue: '"firebase"'
+    },
+    {
+      name: "authorizeUser",
+      type: "(user: FirebaseUser) => Promise<boolean> | boolean",
+      description: "Custom authorization function to determine if a user should be granted access. Called after token verification. By default, checks for the presence of a document in the 'user_access' collection keyed by the user's UID.",
+      isOptional: true,
+    },
+  ]}
+/>
+
+## Environment Variables
+
+The following environment variables are automatically used when constructor options are not provided:
+
+<PropertiesTable
+  content={[
+    {
+      name: "FIREBASE_SERVICE_ACCOUNT",
+      type: "string",
+      description: "Path to Firebase service account JSON file. Used if serviceAccount option is not provided.",
+      isOptional: true,
+    },
+    {
+      name: "FIRESTORE_DATABASE_ID",
+      type: "string",
+      description: "Firestore database ID. Primary environment variable for database configuration.",
+      isOptional: true,
+    },
+    {
+      name: "FIREBASE_DATABASE_ID",
+      type: "string",
+      description: "Alternative environment variable for Firestore database ID. Used if FIRESTORE_DATABASE_ID is not set.",
+      isOptional: true,
+    },
+  ]}
+/>
+
+## Default Authorization Behavior
+
+By default, `MastraAuthFirebase` uses Firestore to manage user access:
+
+1. After successfully verifying a Firebase ID token, the `authorizeUser` method is called
+2. It checks for the existence of a document in the `user_access` collection with the user's UID as the document ID
+3. If the document exists, the user is authorized; otherwise, access is denied
+4. The Firestore database used is determined by the `databaseId` parameter or environment variables
+
+## Firebase User Type
+
+The `FirebaseUser` type used in the `authorizeUser` function corresponds to Firebase's `DecodedIdToken` interface, which includes:
+
+- `uid`: The user's unique identifier
+- `email`: The user's email address (if available)
+- `email_verified`: Whether the email is verified
+- `name`: The user's display name (if available)
+- `picture`: URL to the user's profile picture (if available)
+- `auth_time`: When the user authenticated
+- And other standard JWT claims
+
+## Related
+
+[MastraAuthFirebase Class](/docs/auth/firebase.mdx)

package/.docs/raw/reference/cli/dev.mdx

@@ -72,6 +72,12 @@ mastra dev [options]
       description: "display help for command",
       isOptional: true,
     },
+    {
+      name: "--https",
+      type: "boolean",
+      description: "Enable local HTTPS",
+      isOptional: true,
+    },
   ]}
 />
 
@@ -161,7 +167,7 @@ Workflows are expected to be exported from `src/mastra/workflows` (or the config
 
 ## Additional Notes
 
-The port defaults to 4111. Both the port and hostname can be configured via the mastra server config. See [Launch Development Server](/docs/server-db/local-dev-playground) for configuration details.
+The port defaults to `4111`. The port, hostname, and HTTPS settings can also be configured via the Mastra server configuration. See [Launch Development Server](/docs/server-db/local-dev-playground) for configuration details.
 
 Make sure you have your environment variables set up in your `.env.development` or `.env` file for any providers you use (e.g., `OPENAI_API_KEY`, `ANTHROPIC_API_KEY`, etc.).
 

package/.docs/raw/reference/client-js/agents.mdx

@@ -47,7 +47,7 @@ const response = await agent.generate({
     },
   ],
   threadId: "thread-1", // Optional: Thread ID for conversation context
-  resourceid: "resource-1", // Optional: Resource ID
+  resourceId: "resource-1", // Optional: Resource ID
   output: {}, // Optional: Output configuration
 });
 ```
@@ -207,7 +207,7 @@ const response = await agent.generateVNext(
   "Hello, how are you?",
   {
     threadId: "thread-1",
-    resourceid: "resource-1",
+    resourceId: "resource-1",
   }
 );
-```
+```

package/.docs/raw/reference/client-js/memory.mdx

@@ -57,7 +57,7 @@ Update thread properties:
 const updated = await thread.update({
   title: "Updated Title",
   metadata: { status: "resolved" },
-  resourceid: "resource-1",
+  resourceId: "resource-1",
 });
 ```
 

package/.docs/raw/reference/client-js/tools.mdx

@@ -44,6 +44,6 @@ const result = await tool.execute({
     param2: "value2",
   },
   threadId: "thread-1", // Optional: Thread context
-  resourceid: "resource-1", // Optional: Resource identifier
+  resourceId: "resource-1", // Optional: Resource identifier
 });
 ```

package/.docs/raw/reference/core/getWorkflow.mdx

@@ -46,4 +46,3 @@ mastra.getWorkflow("testWorkflow");
 ## Related
 
 - [Workflows overview](../../docs/workflows/overview.mdx)
-- [Dynamic workflows](../../docs/workflows/dynamic-workflows.mdx)

package/.docs/raw/reference/core/getWorkflows.mdx

@@ -41,4 +41,3 @@ mastra.getWorkflows();
 ## Related
 
 - [Workflows overview](../../docs/workflows/overview.mdx)
-- [Dynamic workflows](../../docs/workflows/dynamic-workflows.mdx)

package/.docs/raw/reference/core/setTelemetry.mdx

@@ -31,5 +31,5 @@ This method does not return a value.
 
 ## Related
 
-- [Telemetry overview](../../docs/observability/telemetry.mdx)
-- [Telemetry reference](../../reference/observability/telemetry.mdx)
+- [Logging](../../docs/observability/logging.mdx)
+- [PinoLogger](../../reference/observability/logger.mdx)

package/.docs/raw/reference/storage/postgresql.mdx

@@ -112,3 +112,194 @@ This enables direct queries and custom transaction management. When using these
 
 This approach is intended for advanced scenarios where low-level access is required.
 
+## Index Management
+
+PostgreSQL storage provides comprehensive index management capabilities to optimize query performance.
+
+### Automatic Performance Indexes
+
+PostgreSQL storage automatically creates composite indexes during initialization for common query patterns:
+
+- `mastra_threads_resourceid_createdat_idx`: (resourceId, createdAt DESC)
+- `mastra_messages_thread_id_createdat_idx`: (thread_id, createdAt DESC)  
+- `mastra_traces_name_starttime_idx`: (name, startTime DESC)
+- `mastra_evals_agent_name_created_at_idx`: (agent_name, created_at DESC)
+
+These indexes significantly improve performance for filtered queries with sorting.
+
+### Creating Custom Indexes
+
+Create additional indexes to optimize specific query patterns:
+
+```typescript copy
+// Basic index for common queries
+await storage.createIndex({
+  name: 'idx_threads_resource',
+  table: 'mastra_threads',
+  columns: ['resourceId']
+});
+
+// Composite index with sort order for filtering + sorting
+await storage.createIndex({
+  name: 'idx_messages_composite',
+  table: 'mastra_messages',
+  columns: ['thread_id', 'createdAt DESC']
+});
+
+// GIN index for JSONB columns (fast JSON queries)
+await storage.createIndex({
+  name: 'idx_traces_attributes',
+  table: 'mastra_traces',
+  columns: ['attributes'],
+  method: 'gin'
+});
+```
+
+For more advanced use cases, you can also use:
+- `unique: true` for unique constraints
+- `where: 'condition'` for partial indexes
+- `method: 'brin'` for time-series data
+- `storage: { fillfactor: 90 }` for update-heavy tables
+- `concurrent: true` for non-blocking creation (default)
+
+### Index Options
+
+<PropertiesTable
+  content={[
+    {
+      name: "name",
+      type: "string",
+      description: "Unique name for the index",
+      isOptional: false,
+    },
+    {
+      name: "table",
+      type: "string",
+      description: "Table name (e.g., 'mastra_threads')",
+      isOptional: false,
+    },
+    {
+      name: "columns",
+      type: "string[]",
+      description: "Array of column names with optional sort order (e.g., ['id', 'createdAt DESC'])",
+      isOptional: false,
+    },
+    {
+      name: "unique",
+      type: "boolean",
+      description: "Creates a unique constraint index",
+      isOptional: true,
+    },
+    {
+      name: "concurrent",
+      type: "boolean",
+      description: "Creates index without locking table (default: true)",
+      isOptional: true,
+    },
+    {
+      name: "where",
+      type: "string",
+      description: "Partial index condition (PostgreSQL specific)",
+      isOptional: true,
+    },
+    {
+      name: "method",
+      type: "'btree' | 'hash' | 'gin' | 'gist' | 'spgist' | 'brin'",
+      description: "Index method (default: 'btree')",
+      isOptional: true,
+    },
+    {
+      name: "opclass",
+      type: "string",
+      description: "Operator class for GIN/GIST indexes",
+      isOptional: true,
+    },
+    {
+      name: "storage",
+      type: "Record<string, any>",
+      description: "Storage parameters (e.g., { fillfactor: 90 })",
+      isOptional: true,
+    },
+    {
+      name: "tablespace",
+      type: "string",
+      description: "Tablespace name for index placement",
+      isOptional: true,
+    }
+  ]}
+/>
+
+### Managing Indexes
+
+List and monitor existing indexes:
+
+```typescript copy
+// List all indexes
+const allIndexes = await storage.listIndexes();
+console.log(allIndexes);
+// [
+//   {
+//     name: 'mastra_threads_pkey',
+//     table: 'mastra_threads',
+//     columns: ['id'],
+//     unique: true,
+//     size: '16 KB',
+//     definition: 'CREATE UNIQUE INDEX...'
+//   },
+//   ...
+// ]
+
+// List indexes for specific table
+const threadIndexes = await storage.listIndexes('mastra_threads');
+
+// Get detailed statistics for an index
+const stats = await storage.describeIndex('idx_threads_resource');
+console.log(stats);
+// {
+//   name: 'idx_threads_resource',
+//   table: 'mastra_threads',
+//   columns: ['resourceId', 'createdAt'],
+//   unique: false,
+//   size: '128 KB',
+//   definition: 'CREATE INDEX idx_threads_resource...',
+//   method: 'btree',
+//   scans: 1542,           // Number of index scans
+//   tuples_read: 45230,    // Tuples read via index
+//   tuples_fetched: 12050  // Tuples fetched via index
+// }
+
+// Drop an index
+await storage.dropIndex('idx_threads_status');
+```
+
+### Schema-Specific Indexes
+
+When using custom schemas, indexes are created with schema prefixes:
+
+```typescript copy
+const storage = new PostgresStore({
+  connectionString: process.env.DATABASE_URL,
+  schemaName: 'custom_schema'
+});
+
+// Creates index as: custom_schema_idx_threads_status
+await storage.createIndex({
+  name: 'idx_threads_status',
+  table: 'mastra_threads',
+  columns: ['status']
+});
+```
+
+### Index Types and Use Cases
+
+PostgreSQL offers different index types optimized for specific scenarios:
+
+| Index Type | Best For | Storage | Speed |
+|------------|----------|---------|-------|
+| **btree** (default) | Range queries, sorting, general purpose | Moderate | Fast |
+| **hash** | Equality comparisons only | Small | Very fast for `=` |
+| **gin** | JSONB, arrays, full-text search | Large | Fast for contains |
+| **gist** | Geometric data, full-text search | Moderate | Fast for nearest-neighbor |
+| **spgist** | Non-balanced data, text patterns | Small | Fast for specific patterns |
+| **brin** | Large tables with natural ordering | Very small | Fast for ranges |
+

package/.docs/raw/reference/workflows/workflow-methods/branch.mdx

@@ -44,5 +44,5 @@ workflow.branch([
 
 ## Related
 
-- [Conditional branching](../../docs/workflows/control-flow.mdx)
-- [Conditional branching example](../../examples/workflows/conditional-branching.mdx)
+- [Conditional Branching Logic](../../../docs/workflows/control-flow#conditional-logic-with-branch)
+- [Conditional Branching Example](../../../examples/workflows/conditional-branching)

package/.docs/raw/reference/workflows/workflow-methods/commit.mdx

@@ -27,4 +27,4 @@ workflow.then(step1).commit();
 
 ## Related
 
-- [Control flow](../../docs/workflows/control-flow.mdx)
+- [Control Flow](../../../docs/workflows/control-flow.mdx)

package/.docs/raw/reference/workflows/workflow-methods/create-run.mdx

@@ -10,7 +10,7 @@ import { Callout } from "nextra/components";
 The `.createRunAsync()` method creates a new workflow run instance, allowing you to execute the workflow with specific input data. This is the current API that returns a `Run` instance.
 
 <Callout>
-For the legacy `createRun()` method that returns an object with methods, see the [Legacy Workflows](../legacyWorkflows/createRun.mdx) section.
+For the legacy `createRun()` method that returns an object with methods, see the [Legacy Workflows](../../legacyWorkflows/createRun.mdx) section.
 </Callout>
 
 ## Usage example
@@ -61,5 +61,5 @@ const result = await run.start({
 
 ## Related
 
-- [Run Class](./run.mdx)
-- [Running workflows](../../examples/workflows/running-workflows.mdx)
+- [Run Class](../run.mdx)
+- [Running workflows](../../../examples/workflows/running-workflows.mdx)

package/.docs/raw/reference/workflows/workflow-methods/dountil.mdx

@@ -47,4 +47,4 @@ workflow.dountil(step1, async ({ inputData }) => true);
 
 ## Related
 
-- [Control flow](../../docs/workflows/control-flow.mdx)
+- [Control Flow](../../../docs/workflows/control-flow.mdx)

package/.docs/raw/reference/workflows/workflow-methods/dowhile.mdx

@@ -47,4 +47,4 @@ workflow.dowhile(step1, async ({ inputData }) => true);
 
 ## Related
 
-- [Control flow](../../docs/workflows/control-flow.mdx)
+- [Control Flow](../../../docs/workflows/control-flow.mdx)

package/.docs/raw/reference/workflows/workflow-methods/foreach.mdx

@@ -57,4 +57,4 @@ workflow.foreach(step1, { concurrency: 2 });
 
 ## Related
 
-- [For each](../../docs/workflows/control-flow.mdx)
+- [Repeating with foreach](../../../docs/workflows/control-flow.mdx#repeating-with-foreach)

package/.docs/raw/reference/workflows/workflow-methods/map.mdx

@@ -40,4 +40,4 @@ workflow.map(async ({ inputData }) => `${inputData.value} - map`
 
 ## Related
 
-- [Input data mapping](../../docs/workflows/input-data-mapping.mdx)
+- [Input data mapping](../../../docs/workflows/input-data-mapping.mdx)

package/.docs/raw/reference/workflows/workflow-methods/parallel.mdx

@@ -40,4 +40,4 @@ workflow.parallel([step1, step2]);
 
 ## Related
 
-- [Parallel workflow example](../../examples/workflows/parallel-steps.mdx)
+- [Parallel Workflow Example](../../../examples/workflows/parallel-steps.mdx)

package/.docs/raw/reference/workflows/workflow-methods/sendEvent.mdx

@@ -46,4 +46,4 @@ workflow.sendEvent('event-name', step1);
 
 ## Related
 
-- [Sleep & Events](../../docs/workflows/pausing-execution.mdx)
+- [Sleep & Events](../../../docs/workflows/pausing-execution.mdx)

package/.docs/raw/reference/workflows/workflow-methods/sleep.mdx

@@ -40,4 +40,4 @@ workflow.sleep(5000);
 
 ## Related
 
-- [Sleep & Events](../../docs/workflows/pausing-execution.mdx)
+- [Sleep & Events](../../../docs/workflows/pausing-execution.mdx)