> 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-2-2026.md).

# November 2, 2026

This update adds the ability to retry activity triggers at a calculated date, archive workflows, and use a record's last modified date to handle updates that arrive out of order. It also includes improvements to related-record lookups and workflow editing.

## Retrying activity triggers at a future date

[Activity triggers](https://docs.middle.app/middle-docs/product/accounts/workflow-triggers.md#activity-based-triggers) now have a **Retry trigger at** option. You can use workflow parameters to calculate when Middle should evaluate the trigger again.

For example, imagine you want to award points after a class. A booking can schedule its trigger to retry after the class, without waiting for another record update or scanning all bookings every day.

When Middle retries, it uses the current record and trigger settings. Changes to the booking's attendance status or class time can therefore affect the result. These scheduled retries do not have a prior record version. Dates in the past or within the next five minutes do not delay the trigger.

You can see pending retries and their dates on the [record's page](https://docs.middle.app/middle-docs/product/accounts/sync/stored-records.md), with links back to the triggers that scheduled them.

## Archiving workflows

You can now [archive workflows](https://docs.middle.app/middle-docs/product/accounts/archive-and-delete-a-workflow.md) you no longer use. This removes them from the normal workflow list and from workflow selection menus, while keeping their history. Archived workflows appear under **Archived workflows** in the account or module navigation.

Before archiving a workflow, remove references to it from triggers and other workflows.

## Using a record's last modified date

App developers can now select a date or datetime attribute under **Last modified date** in a [record type's settings](https://docs.middle.app/middle-docs/product/apps/sync-records.md). This is optional.

For example, two syncs might return different versions of the same member record. If the older version arrives last, it could previously overwrite the newer information. With this setting, Middle compares the dates and keeps the newer version.

When both versions have a valid date, Middle treats an update with the same or an older date as a duplicate. It does not change the stored record or trigger workflows for that update. If either date is missing or invalid, Middle handles the update as it did before.

## Missing related records

Middle now waits longer between attempts to look up a missing related record. The delay increases with each lookup attempt while the record is missing. Additional references to the same missing record no longer keep starting new lookups. This reduces repeated requests for records the source app is not returning.

The record's page now shows how many lookups Middle has attempted, when the record is eligible for another lookup, and whether an automatic lookup is available.

The **Fetch Seen and Unseen Records** option for related-record lookups has been removed. Middle changes existing settings and imported app definitions that use it to **Fetch Unseen Records Only**.

## Other improvements

* Disabling an activity trigger now also prevents [manual replays](https://docs.middle.app/middle-docs/product/accounts/workflow-triggers.md#replaying-triggers) and queued replays from running.
* The [Action selector](https://docs.middle.app/middle-docs/product/accounts/workflow-steps/action.md) in workflow steps is now searchable by action, app, or connection name, and shows which connection the selected Action uses. Organization owners can also open the Action's developer configuration directly from the step.
* Object definitions in the JSON editor now use a list of fields without internal field IDs or an extra root object, making them easier to copy and edit. Older definitions still load.
* Removing a workflow draft is now labeled **Discard draft**.


---

# 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-2-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.
