Output is not a string: Post-mortem of a bug in which we didn't get any support
Today I reported bug #238909, I didn't get any support and my app was broken because of this bug.
Case:
I have an API Call shipped one month ago and never changed after that. Today it stopped working, meaning that my users couldn't use my app.
It looks like BuildShip did an update that corrupted my API Call shipped to production and all the manual copies I had done. Actually, if I duplicate a flow now, the copy misses a lot of fields so it's not functional.
The automatic backup versions didn't work either because of the update. After loosing most of my day working on it, I found out that I just needed to set the Output of my flow as 'object' instead of 'string'. It was a very simple change but it took me hours to find it. That was something I didn't need to do when I shipped my flow, integrated it in my app, tested my app, and released it to production.
It's a big issue. I rely on BuildShip, but I can not trust it because shipped flows change and stop working without any previous warning.
I'm launching my app, fighting to get tracktion. Every user is key to me and the future of my business. I can not afford my app to stop working so many hours.
I can not spend so much time debugging something that was working.
It's great that BuildShip evolves and it's updated. I understand that I may need to update my flow settings to fit the new BuildShip updates when I modify my flow. I may understand if I receive a warning telling me that I have a period of time to update my app if that's required. I can't accept that my shipped flows change and stop working like that. I can't accept that I have flows saved that miss data when I go back to them. That's not the first time that happens.
4 Replies
AI Support Bot Information
<@1026190854693605436> 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
I'm sorry to hear about the inconvenience you've experienced with your API call due to recent updates. I wasn't able to find specific details about bug #238909 or the exact issue you're facing in the documents you provided.
However, I recommend reaching out through the available support channels for more personalized assistance and to ensure that your issue gets the attention it needs. You can submit a support request directly through the "Support" button on your BuildShip Dashboard for detailed help on your specific workflows or to report this bug. Additionally, joining the BuildShip Community on Discord might provide more insights, as you can discuss and share feedback directly with other BuildShip enthusiasts and the team【4:2†buildship-site.json】.
For more detailed or technical concerns, getting in touch with an expert via hiring on the BuildShip platform may also be beneficial .
Please do report this issue through the in-app support if you haven't done so, as it allows the BuildShip team to work on it effectively. You can send a support request using the "Support" button directly from your BuildShip dashboard【4:1†buildship-docs.json】.
BuildShip AI Support
Hey @Luis , if I understood correctly, previously your workflow was working even when output was set to string type?
Hi, @Deepanshu You are right. Actually, I still have two more flows with the same settings in which the output is set to string type, and both of them work.
That's the reason I thought that was a new setting I didn't need to set before. Since they are working in production, I haven't updated them.