> 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/july-2026-release-notes.md). # July 2026 Release Notes ## GRAX Changelog - July 2026 ### Search **Background Search Downloads for All Users** - Large search results now download as background jobs for every GRAX user. When you request a download, GRAX queues the export and notifies you when the file is ready, so you can navigate away while large searches complete. This removes browser timeout errors on searches covering millions of records. **Search Templates for Objects Without Created Date** - Search templates now work for Salesforce objects that do not include a Created Date field. Before this update, applying a date filter through a template on those objects would fail. You can now save and reuse templates against any object GRAX backs up, regardless of whether that object tracks a creation timestamp. *** ### Backup & Restore **CaseComment Records Recovered from Batch Errors** - When a group of CaseComment records fails during backup because Salesforce rejects certain record references, GRAX now automatically isolates the problem records and retries them with a reduced set of fields. Previously the entire batch would fail and those records would be skipped. Orgs with high volumes of CaseComments, or cases with many attachments, will see fewer incomplete backup runs. **Auto-Archive Disabled When Its Salesforce Report Is Deleted** - Scheduled Auto-Archive activities that depend on a Salesforce report now automatically turn themselves off when Salesforce reports the underlying report no longer exists. Before this, a deleted or renamed report caused the activity to fail on every run until someone manually disabled it. **Sandbox Refresh Disables Auto Activities for the Previous Org** - After a Salesforce sandbox refresh, scheduled backup and restore activities tied to the old org are automatically detected and disabled. Running those activities against the refreshed org's new identity would produce incorrect results. This handling is consistent with how GRAX already manages other org-mismatch situations. *** ### Authentication **Unified Domain Selection for Salesforce OAuth** - The Salesforce OAuth connection settings now offer a single unified domain selector instead of separate options for production, sandbox, and custom domains. When connecting a Salesforce org, you select one option that covers all environment types rather than choosing a category first. This reduces the chance of picking the wrong connection type. *** ### Administration **Cloud Storage Bucket Change Blocked When Data Exists** - GRAX now blocks any attempt to change the cloud storage bucket while the current bucket already holds backup data. Switching buckets after data has been stored would cut off access to existing backups without warning. The setting can still be updated in new or empty environments, and a separate override option is available when the change is genuinely intended. --- # 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/july-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.