JonN3
JonN313mo ago

Hi guys @Gaurav Chadha - To pmy

Hi guys @Gaurav Chadha - To pmy previous question, any way I can narrow down where this is? I have no idea where that node is lol
No description
5 Replies
Gaurav Chadha
Gaurav Chadha13mo ago
It says, the issue is in the Fetch Supabase Table node in your workflow. You can check logs too.
JonN3
JonN3OP13mo ago
For sure! I have about 45 nodes of that lol So how can I pinpoint which one is causing the error?
Gaurav Chadha
Gaurav Chadha12mo ago
You can filter out only the Fetch Supabase node and set filter to only failed in logs terminal. This will help in filtering and getting to know which node has issue.
No description
No description
JonN3
JonN3OP12mo ago
hmmm... there are no actual errors its just error in the shipping... The reason I know this is because its now coming back with different nodes each time with errors All of these nodes are just other nodes that have been copied Like where you showed me, I do not see any "workflow" shipping error logs, jsut logs based upon a test run
Gaurav Chadha
Gaurav Chadha12mo ago
Oh, I see, Gotcha. We'll update you, the team checking your workflow and issues you reported earlier. Thank you for your patience and understanding while we work on improving your experience.