Data Protection and Security Toolkit 4.8.0 has been released

🔁 Searches survive a restart or a deploy

A search that was running when the backend restarted used to be lost without a trace: the template stayed locked, the run sat in “In Progress” forever, and nothing ever finished it.

Interrupted runs are now detected and started again automatically. The timeline shows that the run was interrupted and whether it was restarted. Manual, webhook and full-instance runs restart from the beginning; scheduled runs simply continue on their normal schedule.

Because a restarted run rescans from the beginning, actions can be applied a second time to content the interrupted attempt had already reached — a duplicate comment, or a second notification. This is a deliberate trade-off against losing the run entirely, and both the interrupted and the replacement history entries say so explicitly.

Separately, a manual search too large to finish inside a single execution window now resumes from where it stopped. It continues across automatically chained segments that share one history entry, instead of starting over from page one. Deleting a template or uninstalling the app cleans up the saved progress.

💬 Confluence: inline comments and comment replies are now covered

Searches and anonymization actions previously reached only top-level footer comments. They now also cover inline comments, and the replies to both inline and footer comments.

Found items show which comment type a match was in, so it is clear where the content actually sits.

👤 Searches run as the app — the “Actor” field is gone

Templates could name an “Actor” whose identity the app borrowed when writing changes. That made the app’s own edits look like that person’s edits, and it broke self-trigger filtering: a search could re-trigger on the very changes it had just made.

All searches and actions now run as the app user. The Actor field has been removed from the template editor and existing values are ignored — nothing needs to be reconfigured on your side. Content restriction actions continue to use the template owner.

Manual searches also run in a background worker again, so starting one no longer blocks the interface.

✉️ Sending limits for email notifications

A misconfigured template could previously send thousands of emails in a single run through the shared mail service. There is now a ceiling: at most 500 emails per search run, plus rolling limits per day, per hour, and per recipient.

A blocked email appears in the search history as a skipped action naming the limit that stopped it, so nothing fails silently.

Instances sending through their own custom SMTP server are not subject to these limits. Custom SMTP now requires a sender address, and the sender email field is available in Settings.

🔓 Unrestrict a page from the Check case dialog

Once a “Restrict view and edit” action has run successfully, the Check case dialog offers an “Unrestrict” option. It removes all user and group restrictions from that page, with a warning about the consequence before you confirm.

📢 Announcements now appear on custom domains

Announcements now show on sites served from a customer-owned custom domain. Admins on those sites could previously configure a banner and never see it.