This release finishes out the Summer '26 cycle with a round of Slaybot reliability improvements. Slaybot is significantly faster, with image evaluation now running in parallel rather than serially. It also no longer freezes the browser tab when Graphics Acceleration is disabled, detecting that configuration and disabling itself with a warning instead.

Automation & Reliability

Slaybot processing speed has been significantly improved. The halt functionality has been removed, and image evaluation now runs in parallel rather than serially. The practical result is a much faster time from component load to Slaybot completing its run. The legacy File Slayer component detects when Graphics Acceleration is disabled in a user's browser. Without Graphics Acceleration, Slaybot is automatically disabled, and a clear warning is displayed in the component to prevent the browser tab from becoming unresponsive.

Slaybot Froze the Browser When Graphics Acceleration Was Disabled — When Graphics Acceleration was disabled in a user's browser, and Slaybot was enabled on the component, the browser tab would become completely unresponsive. Slaybot is now automatically disabled in this scenario, and a warning message is displayed in the component. (v4.29)

Slaybot Errors When Standard Email Composer Was Open — If Slaybot deleted an inline image while the standard email composer was open, the composer would throw "invalid cross-reference id" errors. All Slaybot delays have been removed, so images are processed as quickly as possible after component load, minimizing the window during which this conflict could occur. (v4.27–v4.28)

License Check Failed for Files Related to User Records — When a file was linked to a User record, the license check threw an exception while searching for User.OwnerId, which could silently prevent deduplication from running. The ownership utility has been updated to handle User record relationships correctly. (v4.27)

ENTITY_IS_DELETED Errors Halted the Entire Slaying Batch — If a file was manually deleted by another process before File Slayer could process it, an ENTITY_IS_DELETED error was thrown that caused the entire batch to fail — no files in that transaction would be slayed. File Slayer now ignores already-deleted files and continues processing the remaining files in the batch. (v4.26)