moritz
moritz3mo ago

❗Sudden outage/error in the 'Get Firestore Document' Node?

Until about an hour ago my Workflow worked perfectly. Suddenly I am getting messages from my users about the app no longer working. I've got loads of errors I cannot explain. @Gaurav Chadha and Buildship team is it something you are aware of?
No description
7 Replies
AI Support
AI Support3mo ago
Hi, it sounds like you might be encountering an issue specific to your workflow or a temporary service disruption. Since this problem has just started occurring, it would be best to submit a support request through the in-app support button for a more immediate and thorough investigation by the BuildShip team. For more information on troubleshooting workflows, you can refer to the BuildShip documentation here. If the issue persists, please provide more details about the errors you are encountering, and the support team will assist you further.
Gaurav Chadha
Gaurav Chadha3mo ago
@moritz can you delete and add the affected nodes again? It should solve this issue, as it seems the node Ids are getting cached.
AI Support
AI Support3mo ago
It sounds like you might be experiencing an issue with node IDs getting cached. To resolve this, you can try deleting and re-adding the affected nodes in your workflow. For more information on managing nodes, you can refer to the following documentation link: Node Management If the issue persists, please submit a request via the in-app support button for further assistance.
What is a Node? – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
moritz
moritz3mo ago
@Gaurav Chadha I just tried that, it's still not working. What's the best way to proceed?
No description
AI Support
AI Support3mo ago
For further assistance, please submit your issue via the in-app support button. This will allow our support team to investigate and provide a tailored solution.
moritz
moritz3mo ago
I re-deployed the whole workflow which solved the problem.
AI Support
AI Support3mo ago
It sounds like re-deploying your workflow resolved the issue you were experiencing. If you encounter further problems or need additional assistance, you can always submit a request via the in-app support button. For more detailed information on deploying workflows, you can refer to the BuildShip documentation on shipping an API.