Release Notes

Version 3.604

Fixes

Batch Executions now complete reliably under heavy async load

In orgs running a very large number of concurrent asynchronous jobs, some batch Executions could fail to update their status to Completed because of row-lock contention. Executions now record their final status reliably, even in the most demanding environments.

Execution record page auto-refresh is limited to the running user

When a user views the record page of an Execution that is still in progress, the page refreshes the Execution’s statistics and status automatically. Previously, this refresh ran for any user viewing the page, which could cause chained batch jobs to run as that user instead of the original running user. It now runs only for the user who is running the Execution, so other users can view the page without affecting the run.

Changes

Column Filter fields renamed, with updated help text

Six Column Filter fields have new names and API names for better readability and consistency, and their help text has been rewritten for clarity. If you have configured any of these fields, copy their values to the new fields after upgrading.

Previous API NameNew API Name
QShowColumnFilter__cQColumnFilterEnabled__c
QFilterableColumnFieldNames__cQColumnFilterFields__c
QPinnedColumnFilterFieldNames__cQColumnFilterPinnedFields__c
QPinnedColumnFiltersHeaderLimit__cQColumnFilterPinnedLimit__c
QExistingValueFilterFieldNames__cQColumnFilterDataOptionFields__c
QColumnFilterDefaultFieldName__cQColumnFilterDefaultField__c

For the updated field descriptions, see Data List Settings.