Centercode Release Notes
Back to all updates

Weekly patch - July 26, 2026

by Ian Nicholson
Fixes

Test Planning

Product Verification Stays Published Like It Should

What we fixed: Product Verification was quietly flipping to an unpublished state after an admin opened one of its associated macros and came back. Since Product Verification acts as a hard gate, that meant everyone in the trial got stuck until someone noticed and republished it. We fixed it so Product Verification holds its published state.

See it in action:

  1. Open a project with Product Verification published and gating trial access.
  2. Click into one of its associated macros, then head back to the Product Verification page.
  3. Product Verification is still published, right where you left it. 🎉

Good to know: Product Verification now only unpublishes when you choose to do so yourself.

Email

Large Email Resends No Longer Hit an Error

What we fixed: Resending a big batch of community-level email at once (think 100 at a time) could throw a server error. We fixed it so large batches go through without a hitch.

See it in action:

  1. Head to a community-level email with a hefty queue.
  2. Resend a large batch, for example 100 recipients.
  3. It sends without a hitch, no need to break it into smaller chunks. 🎉

Form Engine & Custom Surveys

AI-Generated Surveys Point Conditionals at the Right Question

What we fixed: When AI built or imported a survey with conditional logic, the branching rules landed on the wrong question, consistently one spot off. That meant admins had to fix each one by hand. We tightened up the logic so conditionals now point to the question they were actually meant for.

See it in action:

  1. Use AI survey creation to generate a survey that includes conditional (display or branching) logic.
  2. Review each conditional against your element list.
  3. Everything points where it should, no manual cleanup needed. 🎉

Good to know: We also tightened up how character limits are handled during AI survey creation as part of this fix.

Feedback

Summary Prompt Enhancements No Longer Disable AI Reply Generation

What we fixed: Adding a prompt enhancement to summary generation had a side effect: it switched off AI reply generation and wiped out its custom prompt. We fixed it so these two settings stay independent of each other.

See it in action:

  1. Turn on both AI reply generation and summary generation in Feedback collaboration.
  2. Add a prompt enhancement to summary generation.
  3. Your AI reply generation setting and its custom prompt stay exactly as you left them. 🎉

AI-Enhanced Feedback Keeps Its Formatting

What we fixed: When AI enhancement ran on a multi-line or rich-text feedback element, the enhanced version flattened everything into one run-on paragraph, losing line breaks and italics. We fixed it so the enhanced view keeps the structure the original author intended.

See it in action:

  1. Open a feedback item with AI enhancement enabled on a rich-text element that has line breaks and italics.
  2. Toggle to the AI-enhanced version.
  3. Line breaks stay as separate lines and italics stay italic. 🎉

Onboarding/Recruiting

Revoke Pending Invitations Through the Onboarding API

What we fixed: The onboarding (user import) API only worked one way. You could push users into a pool, but there was no way to pull an unused invitation back out without going into the platform directly. We added a revoke counterpart to the add endpoint, so integrations can cancel a pending invitation programmatically.

See it in action:

  1. Add a user to an onboarding pool via the API, as you do today.
  2. Call the new revoke endpoint with the same email you used to add them.
  3. That pending invitation can no longer be consumed. The person only gets back in through a fresh invitation. 🎉

Good to know: This only affects pending invitations, anyone who already joined is unaffected. The revoke endpoint requires the encoded email as a parameter to succeed.

Data Engine & Custom Reports

SSO Source and Integration ID Line Up in Reports

What we fixed: In custom reports, the SSO source and SSO integration ID columns sorted their multi-value entries in different orders, making it tricky to tell which ID matched which source. We fixed it so both columns order their entries the same way.

See it in action:

  1. Create a custom report showing SSO source and SSO integration ID.
  2. Check a member with more than one SSO source.
  3. The sources and their IDs line up in the same order across both columns. 🎉