Hello!
I've seen a lot of topics that describe the problem with referring startTrigger.data - I've got it also.
I also have a problem that now branch blocks do not run anymore with Internal Server Error
What's wrong?
Hello!
I've seen a lot of topics that describe the problem with referring startTrigger.data - I've got it also.
I also have a problem that now branch blocks do not run anymore with Internal Server Error
What's wrong?
Hi @dsitnik - welcome to the forums.
I was having this issue too, but it seems to have been resolved for me. I just tried creating a branched workflow which worked fine for me (granted it was nothing fancy, but it did reference the startTrigger and a query to a DB). Have you tried closing out the workflow and re-opening it? Sorry, I know that is an annoying answer, but humor me...
I still experience this
it might just be checkVer
blocking the connecting lines or something, but it looks like you have the input for the checkAction
block connected to the webhookReturn1
input... which would mean both blocks are 100% unreachable. workflow execution would either silently finish after checkView
, timeout after the max workflow execution time is reached(run-time error) or if there is another block connected to one of those inputs, it could make compile-time/linter errors
its not possible to connect inputs
Hi @dsitnik
I also was not able to reproduce this bug. Have you tried making a new workflow? Not the ideal solution, but could unblock you.
Are you on cloud?
just to add a couple things to @AbbeyHernandez's suggestion/question that might help us find the source of this:
Inputs
window for the branch blocks, are the previous blocks showing up w values (not grayed out)? sometimes I catch blocks not realizing they're connecting to things when they are... I don't think I normally get that error you're seeing but Switch block
to JS Block(or make new blocks i guess) : if(getMacReport.data[0].report_version === startTrigger.data.report_variant){ return true; } else{ throw Error("checkVer error"); }
Global Error Handler
. you can use { error: workflowContext.currentRun.error }
for the code.Switch block
feature was used to turn them into branch blocks?startTrigger -> getMacReport
and re-connect the startTrigger to the copy:startTrigger -> getMacReport_copy ->
checkVer_copy::if -> checkAction_coppy
checkVer_copy::else -> webhookReturn5_copy