September 28, 2026

This update contains a fix for an issue with the "prior version of a record" feature, which would cause records who existed, but whose last update was behind the general data retention horizon to say that there was no prior version.

This update also includes some usability improvements for workflows.

Prior version and data retention issue

The "prior version of a record" feature depends on an internal "activity history" table, which (prior to today) stored a snapshot of the given update. E.g., if a User record's email is updated, this internal table would show the updated email.

But, data deletion for this internal table is governed by the general data retention horizon for an installation, which is typically kept small for compliance and cost. This meant that for cases where we had a record, but no "activity history" (possible if a record type's deletion is overridden, or if there was recent "purposeful use"), the Trigger system would find no "prior version" even though Middle did have that information.

This internal "activity history" table has now been reworked to store the prior snapshot instead of a snapshot of that update. In this way, Middle will now always know the prior version of a record every time it is updated.

Other improvements

Workflow configuration errors show a warning in the left navigation bar, to help draw attention to the issue.

"Update CRM" has a configuration error

Improved error reporting for variable shadowing in Modules. (In Modules, if a module-level variable is defined with the exact same name as a workflow variable, this is now treated as a configuration error in the UI when viewing or editing the workflow. While the workflow will still run, and will use the workflow-level variable, but users are strongly encouraged to choose unique names.)

Several improvements have been made to the record timeline, including streamlining the diff on record updates.