Implementing Pagination in Okta workflows - "Call Flow" card limitation

Workflows Questions
1

Hello Okta team, I am working on Okta workflows and here is my use case I need guidance on:

I have a main flow that sends the Get Reviews API URL and an empty list to a child flow. The child flow accesses the URL, extracts “data” and “_links” from the response, and adds the “data” to the empty list, which is then called the updated results list. If “_links” contains a “next” URL, the child flow sends this URL and the updated results list back to itself.

This process repeats until there is no more “next” link in _links. The final updated results are then returned to the main flow through a return card, which outputs all the records from the Reviews API.

However, the “Call Flow” card in the main flow returns null if the child flow sends more than certain number of records (more than 50 in my case).

Does the “Call Flow” card have any limitations that would cause this issue?

How can I resolve this problem?

2

Have you tried using the Streaming CAPIA functionality which should handle pagination for you?

3

I have tried using the Streaming API functionality with the List Reviews and List Campaigns APIs. However, it appears that the Get [Streaming] is not functioning as expected for these APIs. Instead of handling pagination automatically, it is behaving like a regular Get request and only returns the first page of results.

4

I’m curious if you’ve shared this with the Support team? I’m wondering if this is a bug or just a known limitation because the Reviews API handles pagination differently in some respect, etc.

1 Like
5

Thank you for your response. I haven’t yet contacted the Support team. The List Reviews API does provide a next URL in the response, indicating support for pagination. However, I’m unsure why this isn’t functioning with the Streaming API. As you mentioned, this might be a known limitation or a potential bug.

6

Yeah, I’m curious to know why that wouldn’t work. Unfortunately, I’m guessing that the way the next link or cursor is structured may differ between the two APIs. It might be worth contacting Support to confirm and see if it’s a bug or if it makes sense to request a feature enhancement via Okta Ideas.

To get over your current roadblock and build pagination, it might help to look at this:

7

ran across the same problem as you. just posted my example Example of Paginated API Response to Parent Flow (recursive flow)