I'm wondering about the pagination support of of the API. For example the

/api/flow_runs/filter

endpoint uses offset based pagination and supports

offset

and

limit

in the payload, where as

/api/events/filter

uses cursor based pagination with only a

limit

parameter and and the return of a

next_page

token to be used in

/api/events/filter/next

. Is something changing around how pagination is handled? I.e. would flow_runs support cursor based pagination in the future or would the events part get an "offset" parameter as well? Or is this something that was just done for performance reasons of the event endpoint?