Cannot Deploy/Ship via Flow Builder 2.0
Dear team,
I have lodged a ticket, but I do some help urgently.
I changed to "Flow Builder 2.0" for one of the flows.
I was able to test the entire workflow which was successfully, however, I cannot deploy or ship it. It says "Failed" without further information. Please help urgently.
Solution:Jump to solution
Hi @Christopher30 @jeff_sss Thank you for being so patient while we worked on fixing this issue, the branch node and the boolean type are now fixed, you can delete the branch node and add it again from the node explorer and try again, it should process the conditions correctly.
38 Replies
AI Support Bot Information
<@1062213785990991972> 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 Response
It seems there isn't specific information from the document searches about solving deployment issues with "Flow Builder 2.0" in BuildShip. Since your problem is urgent and outside the current information, here are a few general troubleshooting steps that might help:
1. Check for Errors: Review if there are any error logs provided by the platform which might indicate what aspect of the deployment is failing.
2. Verify Configuration: Ensure that all configurations related to deployment settings are correct. This might include verifying API keys, permissions, or environment settings.
3. Platform Updates: Make sure that all platform updates and dependencies are current, as older versions might have certain unresolved issues.
4. Network Connection: Sometimes connection issues can prevent deployment. Ensure that your network connection is stable and that any necessary ports are open.
5. Support Request: Since the issue might be specific or complex, please send a support request through the BuildShip app for specialized assistance. They might also provide logs or error codes that could help in identifying the issue more clearly.
If you need more structured guidance, consider reaching out directly via their support form or email【4:8†buildship-site.json】.
BuildShip AI Support
the problem is that there is no information, i do not even know what went wrong while everything worked fine in v1
I have the same issue. Built a new workflow using V2. Trying to deploy it, but it fails. However, when I run a test, all nodes work without any errors.
Gee, Chris, hopefully you are not in the same category like me, I have used 10+ flows in my owner business (500K credits per month consumption) at the moment, and I lost 80% of the working flows so far. Desperately need a solution, and I am very frustrated.
I have lodged a ticket with BuildShip today, so far not response as yet.
No, it sounds like you are in a worse situation than me. I am just trying to build some new flows to launch a product.
I tried to deploy some generic test workflow by adding only a trigger and a node that scrapes data from a URL. That worked.
Then I tried to add the "Postgres Fetch Table Data" node but didn't change anything in the code and the deployment Failed. However, if I test the node, it works perfectly fine.
@Gaurav Chadha
yeah, that is the frustration, nothing is changed, but yet, the v2 broke the flow even the testing is successful
Hey @Christopher30 @jeff_sss we are working the fix for the deployment/ship issues on priority, will update you soon.
Thank you for your patience
@Gaurav Chadha thanks for getting back to us. I also noticed that the v1_archive is there, this is working as a fall back solution
any updates on this thread as of yet?
one of my main flow still has the same issue. This time, it has an error message: Invalid Workflow
Other small one seems to be working now.
Yes - that's been my problem. I converted to 2.0, changed the trigger from a GET REST API endpoint to a CRON, and despite it manually testing perfectly well, when I click 'Ship' I get a "Failed: Invalid workflow Connected triggers" error.
same here, just tried again, dont think the problem has been resolved as yet.
Same here. I can't ship a workflow that uses Postgres nodes. But was able to ship a workflow which uses one custom-made node (the whole workflow is super short, just REST API trigger, one custom-made node, and output).
As someone wrote a couple of days ago in the general channel, I love and hate Buildship at the same time. I already started yesterday to use another platform for my backend tasks and will leave on Buildship only those functions that I haven't figured out how to do somewhere else (because of imported libraries).
Hi @Christopher30, is it on the new flow Postfres nodes or migrated flow?
@jeff_sss @Nayls @Christopher30 We have made fixes and released it, could you please try to migrate your V1 workflow to V2 using the Flow Builder Button?
Let me know if you get into issues, and share it via in-app support.
Please note: it will only work on the workflows you'll migrate now, (previously migrated workflows won't be updated)
@Gaurav Chadha It is a flow built on V2. + The Postgres node is not edited and it works in test mode, but deployment fails.
One thing to mention - last week when I was doing my account's migration to V2, it first showed that the migration failed, but the whole system was still updated to v2 and the new functionality was ready for using.
is it only happening on the postgress node? Can you try to delete and add the node again from the explorer? If it still doesn't work you can submit a new support request via in-app support.
@Gaurav Chadha I have not only tried to delete and add the node again, but I also have tried to start a new workflow, it still gives the same error.
@Gaurav Chadha - I'm having the same issue as Christopher30 - for ANY 2.0 workflow I create - even net new - I get the following error 'Failed: Invalid workflow Connected triggers'.. here's a really simple example:
Are there any updates about your situation @jeff_sss?
after the fix by the team, it is working now, I converted the biggest flow in BuildShip with a bit of tweaking, and it is working fine now. Thanks @Gaurav Chadha
and thank you @Christopher30 and @Nayls for promoting this thread
wait, I spotted another bug in V2, lodged a ticket with BuildShip (#650516).
basically, when the condition is true, it triggers the false route. I set the other way around, same thing.
@Christopher30 @Nayls Can you also please share your workflow via in-app support with a jam.dev recording? It will help us speed up the solution for this.
I will record it tomorrow @Gaurav Chadha
Btw, I also submitted the ticket earlier this week mentioning the same error that @jeff_sss is talking about - the condition on the branch node was true, but the workflow executed (in test mode) the "else" branch side.
We are tracking this error and will update a fix shortly. Thanks all for reporting this.
Hi @Gaurav Chadha - I'm still having the issue: https://jam.dev/c/8f63eaad-e696-4d5c-965f-9c7bc724ce8a
Jam
Jam | Console logs, network requests, and more
Click this link to see the video on app.buildship.com, with console logs, network tab and device information.
Hi @Gaurav Chadha , Good news—I tried again today to add the "Postgres Fetch Table Data" node and deploy the workflow. It finally worked, and I was able to ship the workflow!
Hopefully, it wasn't just a one-time thing and it will also work in the future.
@Gaurav Chadha - I'm seeing different errors now.. "Failed: Internal error, workflow schema is invalid. Please contact support."
Im having the same issue? It hasn't been solved right?
yes - my issues haven't been solved as of yet.
Hi @Board of Innovation @Nayls you should now get a different error message, also if its a V1 to V2 migrated workflow, could you please try to migrate it again and try to deploy?
@Gaurav Chadha - confirming I can now connect either a cron and/or a rest API endpoint to my flows in V2. Thanks for helping with this issue!
Trying to ship a workflow but I keep getting this error although I have skipped the node in question.
Error is as follows:
Failed: Internal error, workflow schema is invalid. Please contact support.
Error in following nodes:
- Update Multiple Field Values is invalid
The node was created in v2 itself, not migrated. Also, the node is working as intended when im testing, and its not showing any error in the code itself. Only when i try shipping, i get this message.
@Gaurav Chadha
Hi @RustInPeace Can you delete and add the node again then try to ship, we have pushed a fix
Solution
Hi @Christopher30 @jeff_sss Thank you for being so patient while we worked on fixing this issue, the branch node and the boolean type are now fixed, you can delete the branch node and add it again from the node explorer and try again, it should process the conditions correctly.
thanks Gaurav for the update. So the original one is not working regardless of what we do now I guess, and the solution now is to add the new branch node, is that correct?
I can confirm that a branch node is working correctly now (I tried it on a new workflow).
Yes