[Unexpected token R in JSON at position 0] when access another workflow
I have 2 very simple workflows: Hello and Access Hello.
In Access Hello workflow I used a API call node to access Hello workflow with its Endpoint URL.
when I test Hello, it works very well. However, when I test Access Hello, it always prompt:
Unexpected token R in JSON at position 0.
Please find the attachment [image]
Why is that? What shoul I do now?
Thanks a lot.
40 Replies
Hi @Jerry It is because you are running a test without passing the required values in the fields.
It is a syntax error in JavaScript, it is not due to the code, or your created BuildShip workflow, it is due to the string or the value you are trying to parse the possible reason for this could be - an empty string, an empty array or an incomplete (a.k.a malformed) JSON data. Does your API which is in the URL requires any query/body/authorization?
@Gaurav Chadha Thank you for your quick reply. the API in the URL requires NO query/body/authorization, just simple as following :
@Gaurav Chadha Would you like to create two very simple workflows for test like I did? Is this a bug in Buildship for now? what can i do now? Thanks!
Yes, some of the nodes are having issues, we are working on fixing nodes, it will be updated soon.
@Gaurav Chadha Good to know. Thank you!
Hi, Hi, Gaurav, when will the issues can be solved and updated? I'm waiting ... ... Thank you.
It should be working fine now, if you try with any API in the API call node.
I tried again. Still the same. Can you double check it ?
Yes, working fine, seems an issue with the API you are creating?
This is mine. Can you find the issue?
Can you test this in editor, or single test of the API call node?
Yes, the same issue, You can try it very quickly on yourself. can you?
Okay, seems only BuildShip APIs testing on BuildShip API call node throwing this error. We'll check for this case.
I tried google.com, still the same.
Can you try this?