I also tried setting a paging token: This seems to go a lot further (I think past 100 items).

Each page gives 100 items . paging token is to get next 100 items, then you can limit the results using "Result limit" field. https://console.apify.com/actors/FNhKFjeL8hWQtMeZI/information/latest/readme

% echo dXJuOmxpOmFjdGl2aXR5OjczMTk1MzA5NTc2NTk1ODY1NjAtMTc0NTExMjE1NjEyNg== | base64 --decode

urn:li:activity:7319530957659586560-1745112156126

From what I see this seems like a simple base64 encode of the activity identifier and the timestamp. Would you be able to play with this to get to a different number of reactions / reactions since a last activity?

you want to provide activity id and get reactions after it? or get more than 100 reactions? didn't get your ask so if you can clarify in details that would be great. thanks

I want to watch all the reactions / comments and posts from a set of profiles. So here is my current plan / workflow:

on init:

• get last 1000 reactions using your regular paging

For refresh - I want to get the minimum number of reactions that I don't know of. For this I,

• get limit=1 reaction, page1 (gives me a paging token)
• get limit=1 reaction, page2 using paging token. Let's call this Rx.

Let's say my local system has reactions 1,2,3,4... Rx, Rx+1, Rx+2 ... Rx+15.

• If I already have Rx locally like mentioned above, that probably means I have a few reactions after it as well. I will count these. Say I have 15 reactions locally that came after Rx. I will requery the first page with 100-15-1 = 84 limit to get ALL the reactions so far.
• If I don't have Rx locally, this means there were >100 reactions. So I will get the first 100 fully and then apply the above algorithm to fill the gaps.

As you can see - I am doing a bunch of steps to minimize cost so that I can watch. It would be much simpler if you can build a date based filter. That's all.