yammering-amber•2y ago
Capture Node malfunctioning!.
Does not move to next node and return with this error.
16 Replies
yammering-amberOP•2y ago
tried the same workflow in different project still getting the error, it just refuses to move ahead.
yammering-amberOP•2y ago
always getting stuck on this node, even tried changing the variables that its being captured on.
Prolly getting stuck on that next block.
The flow doesn't necessarily get stuck where it is highlighted.
yammering-amberOP•2y ago
@W. Williams (SFT) here you see next node is just a simple text saying "wait a sec" it shouldn't be that hard to handle.
what is the next block after that?
yammering-amberOP•2y ago
yes...the issue was with the next step. it was an api call. the endpoint was causing error.
But that was for the original flow
But idk why it refused to move for ways here to the text node
the canvas does not highlight until it has moved through the blocks ahead.
yammering-amberOP•2y ago
Yes that's why I was confused why it didn't go to the text node.
The api was like 2 steps ahead of it.
Does it pre process the api?
it is going to wait until it gets to another stopping point (I think that is what I was told).
yammering-amberOP•2y ago
I see something like capture node.
yes
b/c it sends all the info between captures all as one payload
yammering-amberOP•2y ago
The issue was a timeout error on the endpoint side. Due to encryption key.
This is different from the mistral.
I see why it's important not to have a timeout for API.
so youu have a capture (question) -> ai response -> more text -> more text -> button step = it delivers 3 text blocks and the buttons in one payload
yammering-amberOP•2y ago
I wish you could actually determine the timeout duration and reroute.
Understood.
you can in functions
yammering-amberOP•2y ago
Yea..but this is just a simple API. Don't wanna go through the hassle of writing code and variables.😂
It worked out though after fixing the issues on endpoint.
But I wish there was more information given on this and rerouting abilities...than just "Unable to fetch response". Both on prototype and production bot .