Currently RecordTimelineDataProvider.getTimelineItemData assumes all the data is returned in the initial call to Database.query which results in the timeline not displaying all the records without an indication some records are missing.
When Database.query is called if there are more than a few records in the result, the field done is false and nextRecordsUrl should then be called to fetch the remaining rows.
nextRecordsUrl is potentially returned for each object in the result. So the fix will require iterating through objects in the result, calling nextRecordsUrl where needed and reassembling the result to be returned to the LWC.
Currently RecordTimelineDataProvider.getTimelineItemData assumes all the data is returned in the initial call to Database.query which results in the timeline not displaying all the records without an indication some records are missing.
When Database.query is called if there are more than a few records in the result, the field done is false and nextRecordsUrl should then be called to fetch the remaining rows.
This is described in https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_query.htm
nextRecordsUrl is potentially returned for each object in the result. So the fix will require iterating through objects in the result, calling nextRecordsUrl where needed and reassembling the result to be returned to the LWC.