> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/release-notes/november-10-2026.md).

# November 10, 2026

This update adds lists of pending trigger retries, clearer workflow validation, and more reliable workflow editing. It also improves how related-record IDs are passed to Actions and reduces database work during workflow execution.

## Viewing pending trigger retries

You can now see pending [activity trigger retries](https://docs.middle.app/middle-docs/product/accounts/workflow-triggers.md#activity-based-triggers) across an account or the entire installation.

Open **Pending trigger retries** from an account's **Workflow triggers** page. Organization owners can also open the **Pending trigger retries** tab under **Accounts** to see retries across all accounts.

Each entry shows the retry date, record, trigger, workflow, module, and whether Middle has claimed it for processing. Links take you directly to the related record, trigger, or workflow.

## Clearer workflow validation

Middle now reports an error when a step reads a declared workflow variable that is never assigned anywhere in that workflow version. It also warns when a declared variable is never assigned or never used.

For example, declaring a `member_id` variable does not give it a value. If a step reads it without any step assigning it, Middle now identifies that problem in the editor.

## More reliable workflow editing

Previously, there was a problem with editing workflow titles, text, and descriptions on busier accounts. Your work could sometimes be lost when quickly tabbing between fields. This has been resolved. Saving several title or description changes in quick succession preserves their order, so an older save cannot overwrite a newer edit.

## Related-record IDs in Action inputs and text

Previously, there was a problem with foreign key usage in workflows where you could turn a foreign key into a string or pass it into an action, expecting that Middle would give you the actual ID. But instead, what you would get is a JSON representation of the key. (This JSON representation is what Middle internally uses to resolve foreign keys into actual records. And it wasn't correct that we would give you this JSON representation in a workflow.)

Now we will give you just the ID and not that JSON representation, when passing a foreign key to an [Action](https://docs.middle.app/middle-docs/product/accounts/workflow-steps/action.md), or when turning it into a string values inserted into text.

For example, passing a member reference now sends the member's ID, rather than an object containing Middle's connection information.

Middle keeps the complete reference in saved variables and execution history so it can still identify the correct record. Parameter validation now warns when you use a related-record reference where an ID string is expected and recommends selecting the ID explicitly. Validation also handles object definitions that refer back to one another without failing.

## Other improvements

* Actions that populate [assisted variable choices](https://docs.middle.app/middle-docs/product/modules.md#assisted-variables) now have up to 60 seconds to finish, increased from 10 seconds.
* Workflow execution now batches execution-history saves and record-usage updates, reducing database writes and transaction overhead.
* Large execution traces now respect their storage size limits. Middle omits oversized traces instead of trying to save them beyond those limits. This should help resolve an out-of-memory error that can crash workers for certain large installations.
* Execution history, Action history, record timelines, and error reports now handle deleted workflows, steps, Actions, and records more consistently. Retained IDs remain visible without links to items that no longer exist.
* Fixed scheduled module triggers using the wrong workflow ID when compiling their configuration.
* **Other type** choices now include object definitions from the current workflow version and outputs of Actions used in that version. Copying a workflow or making a new version preserves existing references, including references with validation errors, so you can correct them in the new version.
* The Modules list now has paging controls, calculates the last page correctly, and returns to the first page when you change the search or active filter.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.middle.app/middle-docs/release-notes/november-10-2026.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
