could someone help me with this error. It was working early now when i logged in to the SSD im getting this error in the backend console.
Hello @Aswin ,
Are you seeing this error immediately when you run the program, or does it occur only during a specific operation?
Hi @Aswin ,
Can you check on your app if the is anywhere you are using status.
You can share a screenshot of where you defined it and using it.
This is only showing when i access the details of the book in that time im creating a audit operation so from there this error is causing. But there Im not using any status keyword i was using the session node and passing the session to a variable in bh. when i removed that and removed the console of the session from the script it is working. Let me do once more and if the issue persist i will connect you guys. @Sam @Simphiwe
this is the reason which that error occur.
Could you please tell me what is the error here ? @Sam @Simphiwe
Hello @Aswin ,
Are you using any status variable in createAudit? Please ensure that it is being used correctly and check whether the session is being logged in the console.
No im sure im not using any status variable in createAudit @Sam
Hello @Aswin ,
Is bh.local.session being logged to the console? If an error occurs there, you can try using optional chaining or an if condition to help debug the issue.
I think the error is not with the console the i commented the console part and still the error is there i think its coming from the session node @Sam
Hello @Aswin ,
What I meant is — are you actually getting bh.local.session? if it’s undefined, try using optional chaining or an if condition to debug.
I’m not using the bh.local.session. I was only using that for consoling only as you can see in the previous screenshot. Now im only using the session node and assigning that to bh.local.session. And like i said I’m not using the bh.local.session in the entire flow still I’m getting the error. @Sam
Hey @Sam i got the data now. I think initially i used the session with the startnode not an http in node maybe that was causing the issue. When i tried with the http in node i got the data.