i connected my ivr to n8n workflow through a webhook. the use case is when someone calls to our IVR the flow will start and do some works
to do this first i want to check for the current caller number is already registered in google sheet or not, if not add the number to google sheet then the flow will execute
Problem is when i am checking the caller number already exist or not the google sheet node is not finishing execution instead it keeps executing not not stopping. if i try 10 times some times it is working and most of the time it’s not. i created another web hook from another workflow for testing purpose that is how i was testing. how can i fix this issue
Can you share your workflow, especially the google sheet node? Maybe it is something in the configuration which might be causing it. Also How many records are there in the google sheet?
Ps. side note. I have had some issues with my environments where my Internet security software was being difficult about n8n. (some SSLs it would not completely trust for some reason) which did cause the same kind of issues of things just running for ever. Might be good to try and add an exception for the n8n environment just to be safe. (I use bitdefender)
How many records are there though? Shouldn’t be too many for google to handle but it might be a reason.
It seems It is stuck on waiting for google to answer your request.
Or the other reason I mentioned in my first answer, something funky going on with other software blocking the actual request so it seems it has sent it but it didnt.
That shouldn’t matter, If you just leave it running does it eventaully finish? How do you have n8n installed / running as well is it self hosted, desktop or cloud?
it is self hosted. if i leave it running then it end after 2 minutes giving error ERROR: Cannot read property ‘statusCode’ of undefined
TypeError: Cannot read property 'statusCode' of undefined
at NodeApiError.findProperty (/home/jaison/.nodejs_global/lib/node_modules/n8n/node_modules/n8n-workflow/dist/src/NodeErrors.js:63:22)
at new NodeApiError (/home/jaison/.nodejs_global/lib/node_modules/n8n/node_modules/n8n-workflow/dist/src/NodeErrors.js:179:30)
at Object.googleApiRequest (/home/jaison/.nodejs_global/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Sheet/GenericFunctions.js:43:15)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async GoogleSheet.getData (/home/jaison/.nodejs_global/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Sheet/GoogleSheet.js:35:26)
at async Object.execute (/home/jaison/.nodejs_global/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Google/Sheet/GoogleSheets.node.js:1111:39)
at async Workflow.runNode (/home/jaison/.nodejs_global/lib/node_modules/n8n/node_modules/n8n-workflow/dist/src/Workflow.js:594:28)
at async /home/jaison/.nodejs_global/lib/node_modules/n8n/node_modules/n8n-core/dist/src/WorkflowExecute.js:537:49
That is interesting, I am fairly sure this error means the connection timed out so there could be an intermittent network issue or some content scanning scanning going on for outbound traffic.
If you are able to it would be worth trying it from a different network to see if it has the same impact.
The URL of your instance doesn’t matter, So my thought is when your n8n install is trying to connect to the Google Service it is timing out which is resulting in the StatusCode not found message.
This sort of thing can happen sometimes if there is something going on with the network your instance / server is running on, I would maybe do some checks to make sure there is nothing unexpected happening on that side of things.
It could also be that something is scanning outbound traffic to ensure nothing is accidentally being leaked or for monitoring and that may be getting in the way as well.
I would start by checking the instance environment you are using to see if there is anything odd going on and maybe check the server logs if they available to see if they show any errors with networking.
Best way I can think of would be to check the server setup and environment which is a little bit outside of our support scope.
As a simple test you could try running an nslookup or a curl request to see if that shows any errors, or maybe have a simple workflow that only does the google sheet search to see if that works so you will know if it is workflow related or not.