Reading time: 3 min read
Sitecore Content Hub resolved issues for May 29, 2026
While small, May 29's Content Hub fixes are impactful to your team
Sitecore Content Hub Fixes CKEditor Sync, Integer Bugs
Sitecore’s latest Content Hub update is mostly a bugfix release. That usually means a quick skim and move on, but this one is a bit more useful than that.
The CKEditor sync fix and integer fix both touch the kind of day-to-day friction that burns time for teams working with integrations, custom scripts or search/query logic. There’s also a welcome cleanup around duplicate notifications and a brand kit loading.
What’s changed
According to the changelog, Sitecore fixed:
- The length parameter in Convert video tasks
- CKEditor not reflecting content changes made through the REST API or action scripts when editing M.Content entities
- CreateEntitiesQuery ignoring Integer property filters when the comparison value was passed as an integer instead of a string
- Brand kits failing to load, along with the Brand Assistant icon disappearing, when a user had access to a large number of brand kits
- Duplicate email notifications when transitioning a state flow on an entity with multiple state flows assigned
Why this matters
Not all bugfixes are equal. So what makes this one stand out?
A broken video task parameter is annoying, but the more interesting items here are the ones that affect trust in the platform.
If content updated through the REST API or action scripts does not show up properly in CKEditor, editors can end up second-guessing whether their content is current. That’s exactly the sort of mismatch that creates support noise and manual rechecks.
The integer filter fix is also a good one. If you’ve ever had a query behave differently because a numeric value had to be passed as a string just to work, you already know how brittle that feels. Fixing that makes integration code cleaner and removes one more weird edge case.
Who should care
This update is mostly relevant for:
- Content Hub administrators supporting editorial teams
- Developers working with the Content Hub REST API
- Teams using action scripts to automate content updates
- Anyone building queries or reports that rely on Integer property filters
- Organizations with large brand kit libraries or more complex approval/state flow setups
If your team has been seeing odd editor sync behaviour, missing brand kit UI elements, or duplicate notifications, this release is worth a look.
Practical watch-outs before you move on
There is a limit to what we can conclude from an RSS summary alone, so I would not oversell this as a major platform shift.
Still, a few practical checks make sense:
- Retest any Content Hub automation that writes content and then expects editors to see the update immediately
- Review any query workarounds where integer comparisons were being coerced into strings
- Ask users with lots of brand kits whether the loading issue has actually cleared up in their environment
- Confirm duplicate notification noise is gone in workflows with multiple state flows attached to the same entity
In other words: trust, but verify.
The bottom line
This is not a flashy release, but it does look like a solid maintenance update for teams living in Content Hub every day.
The API-to-editor sync fix and the integer filter correction are the standouts. Those are the kinds of bugs that quietly waste time until they’re gone.
