Article Pagination, Webhook Retry, and Event Delivery Fixes
Release
Author:
Kirill Gaiduk
Changed on:
23 Oct 2026
| Target release date: | 2026-10-26 |
|---|---|
| Release status: | Released |
Description
This release resolves issues with Article pagination in the GraphQL API, webhook retries, and newly created entities whose workflow did not start because the access token expired during the request. It also prepares Single Sign-On (SSO) environments for the PingOne change to opaque refresh tokens. See the Changelog for details.Changelog
GraphQL API- Resolved an issue where the
`articles`and`articlesByLocation`queries could return`hasNextPage: false`before all matching Articles were returned, so clients that follow pagination stopped early. Pagination now continues to the last matching Article, including Articles linked to multiple Fulfillments `articlesByLocation`requests with`first`or`last`above the maximum page size of 500 now return 500 Articles per page with the correct`hasNextPage`or`hasPreviousPage`value- Resolved an issue where, for some SSO users (typically those whose username contains symbols or non-Latin characters), the
`me`query and Sourcing Profile mutations failed with error`S0040E`(Exception while reading username from access token). Fluent Web Apps now load the user's details after sign-in as expected
- Resolved an issue where webhook retries failed for events that identify the entity by
`entityRef`without an`entityId`, for example events for Billing Accounts, Credit Memos, and Return Orders. Retried events, and the Exception event raised after the final retry, now keep the original event's`entityRef`,`rootEntityId`,`rootEntityRef`, and`rootEntityType`
- Resolved an issue where an entity created through a GraphQL mutation, such as an Order, Fulfillment, or Invoice, could remain in its initial status without being processed when the user's access token expired before the orchestration event (
`CREATE`) was sent for the entity. The orchestration event is now delivered, so the entity continues through its workflow. This mostly affected accounts with SSO, where access tokens are short-lived
- PingOne requires opaque refresh tokens for all OpenID Connect (OIDC) applications by March 1, 2027. New PingOne environments now create the Fluent App with the Opaque Token refresh token format
- If PingOne shows the warning "Update this application to use opaque refresh tokens" on the Fluent App in your environment, set the Fluent App refresh token format to Opaque Token. Sign-in to Fluent Web Apps is not affected. See Switch the Fluent App to Opaque Refresh Tokens in PingOne
| Released capability depth: | Fix |
|---|---|
| Release bundle / Capability type: | Platform |
