Hello everyone, this is Joe
I am having some problems with the paging function of the HTTP Request node.
In particular, the Next URL retrieval option does not seem to be able to access the attributes of previous nodes.
The execution relaunches error “Referenced node is unexecuted”.
I somehow have the impression that this happens from the second round of the loop because, if I open the node in error, I can see the previous referenced node’s data.
Not able to post the actual flow here as there are confidential parameters involved, but I can post a couple of images:
Ensure to copy your n8n workflow and paste it in the code block, that is in between the pairs of triple backticks, which also could be achieved by clicking </> (preformatted text) in the editor and pasting in your workflow.
```
<your workflow>
```
That implies to any JSON output you would like to share with us.
The error “An expression references the node ‘Get Access Token’, but it hasn’t been executed yet. Either change the expression, or re-wire your workflow to make sure that node executes first.” would indicate the automatic discovery of the referenced node’s item failed. This is likely due to IF node present in the flow which prevents identifying the item (link it back to the paired item).
To resolve, replace .item. with .first(). to help n8n locate the item. That is, replace the expression {{ $('Get Access Token').item.json.instance_url }} with {{ $('Get Access Token').first().json.instance_url }}. Similarly, you likely need to do that the reference to the node “Create Query Job”.
