Does anyone have advice how to troubleshoot the HTTP Request node pagination “complete expression”?
I’ve provided a completion expression that evaluates to true/false depending on whether the current response includes a “next” page link.
However when executing the node, it acts as if the expression always returns true and stops at the first page. It doesn’t make any additional requests, even though the response does contain a next URL and the completion expression does evaluate to false (at least in the UI preview).
If I set the “complete expression” to “{{ false }}” then it does make more requests, however each request is a repeat of the original one. Even though the node’s “next URL” field contains “page=2” in the UI, when executing, it just keeps replaying the same original request until it reaches the “max pages” limit.
It seems like the next URL and completion expressions operate on different $response data at execution time vs. the UI preview. In the UI, it looks like the evaluated expressions should lead to getting additional pages, but at run time that doesn’t happen.
Is there a way to console.log or otherwise inspect how the expressions are evaluating at run time? Or other ideas how to troubleshoot this?
Hey, I am experiencing a similar problem after updating to version 1.22.6. In my workflow, the HTTP node was working perfectly with pagination, but now it’s only retrieving the first page. Even though my Complete Expression is still false, it doesn’t proceed to the next page.
I have the same issue after updating from 1.20 → 1.22.6
I revered back to 1.22.1 and issue was still present
I ended up reverting back to 1.20.0 and confirmed working proper again
Thanks Jon!
I’ll wait until the next “latest” release since i don’t currently have a development environment to test further in. Appreciate the response and addressing it so quickly!
