Thanks for all the insight here! Endpoints are made by different teams, so there are inconsistencies in how they handle errors and edge cases (as you’re all aware 
) Pointing these out helps me have a conversation with the teams to make them consistent.
I’ll work with the teams to make these consistent OR move to a cursor. The latter is the preferred method going forward (as you can see in most new APIs), but we should absolutely be consistent with our error codes and messaging if the offset is too high or it was an actual server error.