> For the complete documentation index, see [llms.txt](https://documentation.grax.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.grax.com/notices/release-notes/june-2026-release-notes.md). # June 2026 Release Notes ## GRAX Changelog - June 2026 *** ### Search **More reliable search downloads, especially for large result sets** - When you run a search in GRAX, you can now export the results as a downloadable file without copying records by hand. GRAX runs the export as a background job and retries automatically if Salesforce is slow to respond. Only the user who started the download can view or retrieve the result, keeping search exports private by default. *** ### Backup & Restore **FlowOrchestrationLog is now backed up automatically** - The FlowOrchestrationLog object requires explicit Salesforce permissions that many orgs do not have set by default. GRAX now detects when these permissions are missing and applies them automatically if the auto fix permission setting is enabled. This is now active for all Salesforce organizations. **Rich text field backup handles more image and attachment error states** - Rich text fields can contain both embedded images and anchor links that point to external files. GRAX now correctly tells these apart, so an anchor link to a missing or inaccessible file no longer stalls backup of the surrounding record. **File attachment links are now included in backup for all organizations** - Salesforce connects records to their attached files through document link records, GRAX now backs up those links alongside the records themselves. This ensures file attachments stay associated with the correct records when browsing or restoring data. **Apex CPU limit errors no longer stop backup** - Orgs with complex Apex triggers or large data volumes sometimes receive a CPU time limit error from Salesforce during archive jobs. When this happens, GRAX now breaks the affected batch into smaller chunks and retries each piece separately, rather than stopping the whole job. Records that would previously have been missed are now captured. *** ### UI **Turn off navigation links in the GRAX Lightning Web Component** - The GRAX Child Record Viewer Lightning Web Component now supports a no-links mode for Salesforce page layout embeds. When this mode is active, the record title, email view button, and record ID display as plain text instead of links, so users can view the data without clicking through to other pages. Admins can apply this on any layout where navigation away from the record is not appropriate. **Secondary storage sync now shows a record count** - Passive storage sync - used when GRAX mirrors backup data to a second storage location - now shows a count of records waiting to be copied. Admins managing a two-storage setup can see at a glance how many records are still queued, making it easier to confirm that secondary storage is staying current. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://documentation.grax.com/notices/release-notes/june-2026-release-notes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.