Bløødy
Bløødy2mo ago

Unexpected end of JSON input - BuildShip Trigger

Hello, I am struggling to make a buildship triggered workflow work. It looks like it can't be tested directly and shows no logs when I test it from another workflow. The response only says "Unexpected end of JSON input". I would love to know what's happening and how to debug workflows in general. Also, I can see in the Node Logic default code :
logging.log(`Verified request, body: `, req.request.body)
logging.log(`Verified request, body: `, req.request.body)
Where do you see these logs ? Thank you very much !
No description
No description
2 Replies
AI Support
AI Support2mo ago
AI Support Bot Information
<@329919911902314496> you can react on the relevant answer (message) with a ✅ in this thread when you think it has been solved, by the bot or by a human! Anyone can react on this message with a ❌ if the GPT bot is unhelpful or hallucinating answers. Please note: Team members will review and answer the questions on best efforts basis.
AI Support
AI Support2mo ago
AI Response
The error "Unexpected end of JSON input" suggests that your JSON data is being parsed but is incomplete or not in the expected format. This typically happens when there is a missing closing bracket or your server didn't return complete data. Here are some steps to help debug your workflow on BuildShip and view logs: 1. Debugging Workflows: - Ensure that all JSON being sent is correctly formed. Use a JSON validator to check the structure. - Break down your workflow into smaller parts and test each part individually to isolate the issue. 2. Viewing Logs: - The logging.log statement you referenced is for outputting logs. However, if you are unable to see these logs, it could be due to insufficient permissions or the logs not being configured correctly in the setup. - Check the BuildShip dashboard for any available logs or debug output settings. Logs should be accessible from there if they have been properly captured by the system. - Ensure your workflow is set to capture and store logs. You might need to configure this within the settings, or check if there is a dedicated section for viewing execution logs for deployed workflows【4:6†source】. If the issue continues, you might want to contact BuildShip's support using the support feature in the dashboard for personalized help【4:0†source】.
BuildShip AI Support