A Paging Cookie error means that the CRM SDK returned back the exact same paging cookie value as the previous one rather than a new value that would retrieve the next page of data. It has been determined that this is a limitation of the CRM SDK.

When Includes are utilized (e.g. parent/child relationships) the CRM SDK will return a “page” of data for the child records. The proper paging cookie is required to retrieve the next set of records/page. When the Dynamics CRM Connector requests the next page, and the same cookie is returned from the CRM SDK, TIBCO Scribe® Online generates an error similar to the one below.  

Unable to get the next page of data. Dynamics 365 has not advanced the page cookie for Entity:ee_loyaltyprogram, PagingCookie: <cookie page="1"><ee_loyaltyprogramid last="{E7CD676A-F6AF-E611-80EC-C4346BAC3908}" first="{E7CD676A-F6AF-E611-80EC-C4346BAC3908}" /></cookie>

Note: Paging Cookie errors can also occur when date fields have Non-Zero millisecond values.

See the KB article “Dynamics 365 CRM Paging Cookie Error for Dates with NonZero Milliseconds - TIBCO Scribe® Online”

The resolution to this issue is to remove the included child relationships from the Query block.
If the map is referencing child fields via the For Each Child block, then it will need to be replaced with a Fetch block.