I feel like this is something @genietim might be able to help with.

Thanks for the shoutout @Sarah Lane . I do not see an immediate problem, but I believe in your query you also need to specify how many in order to get paginiation working, i.e.:

{ cards(pipe_id: xxx, first: 30, search: { label_ids: xxxx }) { edges { node { id title } } pageInfo { endCursor startCursor hasNextPage } } }'

@genietim  I have added first but it’s keep retuning ‘MA’ as endcursor and startcursor

I have the same problem

moacyr-baptista could you solve this problem?

I just checked and as far as I can see, the cursor “MA” is a valid one and can be used to paginate, the next one will be different. But I admit, it feels a bit fishy, maybe Pipefy staff should help here… can you contact support@pipefy.com and report back?

Thank you!