> 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/may-2026-release-notes.md). # May 2026 Release Notes ## GRAX Product Updates ### May 2026 May brought meaningful improvements across search, backup reliability, and Salesforce connectivity. The standout addition is the ability to download search results directly from GRAX, with email notification when large exports are ready. Connection reliability for Salesforce got stronger, archive workflows became more self-managing, and several quality-of-life improvements landed across the interface. *** ### Backup & Restore #### Salesforce Connections Now Handle Refresh Token Rotation Automatically **What Changed:** GRAX's Salesforce OAuth connection management now automatically handles refresh token rotation, saving updated tokens when they change and continuing without interruption. **Why This Matters:** If your Salesforce organization uses a connected app with refresh token rotation enabled, your GRAX connection now stays active and renews itself without requiring manual reconnection. Backup jobs continue reliably even when tokens cycle on schedule. *** #### Rich Text Field Backfill Is Now More Resilient **What Changed:** The Rich Text Field (RTF) backfill process now handles records with missing or broken inline images gracefully, continuing through to completion regardless of image availability. **Why This Matters:** RTF backfill jobs now complete reliably across your full data set. If you have a stalled RTF backfill, it is worth restarting it so it can run through to completion. *** ### Archive #### Archive Recurrences Now Auto-Disable When Salesforce Marks Objects as Non-Deletable **What Changed:** When an archive recurrence targets a Salesforce object that Salesforce marks as non-deletable, GRAX now automatically disables the recurrence and sends a notification, matching the behavior already in place for other unsupported configurations. **Why This Matters:** Previously, these recurrences would continue running and failing without a clear signal. Now you receive a notification when a recurrence is stopped, so you can review your archive configuration and make adjustments with full visibility into what changed and why. *** ### Search #### Search Results Can Now Be Downloaded, with Email Notification for Large Exports **What Changed:** Search results can now be exported in the background from the GRAX interface. For exports that take more than one minute to prepare, GRAX sends an email notification when the download is ready, including a direct link to retrieve the file. **Why This Matters:** Large search exports no longer require keeping a browser window open and waiting. Start a download, continue your work, and retrieve the results when you get the notification. This makes it practical to export large data sets on demand without disrupting your workflow. *** #### Search Results Load More Smoothly **What Changed:** The search results table now shows a loading indicator while results are being fetched, rather than displaying a partially rendered or transitioning state between queries. **Why This Matters:** The search experience is now more consistent and easier to read. You will always see a clear loading state while your query runs, rather than a blank or flickering table, so it is easy to tell when results are incoming versus complete. *** ### User Interface #### Deprecated Salesforce Authentication Now Shown as a Prominent Banner **What Changed:** Customers still using Username and Password authentication for their Salesforce connection now see a banner-level notice that this method has been deprecated, replacing the smaller inline warning that was shown previously. **Why This Matters:** If your GRAX instance is connected to Salesforce using Username and Password credentials, this banner is a direct call to action. Migrating to OAuth-based authentication now will prevent disruption when the deprecated method is fully retired. Contact your GRAX customer success team if you need guidance on making this change. *** ### How to Get the Most from These Updates * **Try search downloads for your next large export.** If you regularly pull large data sets from Search, start a download and let the email notification do the waiting for you. You will get a direct link as soon as the file is ready. * **Check for stalled RTF backfill jobs.** With the image-handling improvement in place, any RTF backfill that previously stopped on a broken image should now be able to complete. Restart any that are in a stopped state. * **Review archive recurrence notifications.** If any of your archive recurrences were auto-disabled this month, check the notification to understand which objects were affected and whether your configuration needs to be updated. * **Respond to the deprecated auth banner if you see it.** Customers still on Username and Password authentication for Salesforce should plan a migration to OAuth now. Your customer success team can walk you through the process. *** ### Questions or Feedback? Reach out to your GRAX customer success team or contact support at . *** *May 2026* --- # 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/may-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.