
Here, you can see that the setPagination script is logged in the console, but the flow is getting stuck somewhere. It did not reached to response script

Here, you can see that the setPagination script is logged in the console, but the flow is getting stuck somewhere. It did not reached to response script
Hello @Vivek , for calling 2 nodes at a same time I think you can use async node before the 2 nodes
Hi @Vivek,
It also might not be even reaching that response script. Try checking if your data models(total count and find with limit and skip) on your flow runs successfully one by one.
Maybe remove the connector to the response script and add a log node to log bh.local.books or bh.local.totalCount
for the below setPagination script code console give:

console.log("query", bh.input.query);
let page = parseInt(bh.input.query.page) || 1;
let limit = parseInt(bh.input.query.limit) || 5;
let skip = (page - 1) * limit;
bh.local.query = {};
bh.local.limit = limit;
bh.local.skip = skip;
bh.local.findOptions = { limit: limit, skip: skip };
console.log("88888", { page, limit, skip, findOptions: bh.local.findOptions });
return bh;```
@Vivek ,
It doesn’t run the following nodes because of the return at the end of the setPagination script.
Can you please try removing return bh, everything assigned on your bh will be accessible by other nodes on you flow.