"Workflow Schema is Invalid" Error on Deploy Despite Successful Tests
Hi everyone,
I'm facing a problem when trying to deploy my workflow on BuildShip.
Internal tests pass successfully.
Documents are created correctly in Firestore.
All inputs (authIdToken, body, userId, profileId, status, generatedAt, updatedAt) are properly mapped.
The body JSON is correctly formatted.
However, when I deploy, I get this error:
Failed: Internal error, workflow schema is invalid.
Error in following nodes: Create Document is invalid.
I already validated the mappings, variables, and output schema.
The error seems related to the deploy process, not the flow setup.
Has anyone faced something similar?
Any ideas on what might be causing this?
Thanks a lot for any help!
3 Replies
AI Support Bot Information
<@1097726791990390834> 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 appears that the error you're experiencing, "Failed: Internal error, workflow schema is invalid. Error in following nodes: Create Document is invalid," might be related to the structure or configuration of the "Create Document" node in your workflow during deployment. Here are a few potential areas to check:
1. Node Configuration: Ensure that the "Create Document" node is correctly configured. Double-check the input parameters, output mappings, and ensure that they align with the expected schema of the node. Any mismatch or missing configuration might lead to such errors.
2. Schema Validation: Validate the JSON schema if you are using one for inputs or outputs. Ensure that it is well-structured and correctly defined according to the requirements of your project.
3. Testing Environment: If possible, utilize a testing environment to simulate the deployment to catch errors before they occur in production. This could help you identify specific issues within the "Create Document" node.
4. Community and Support: Consider reaching out to BuildShip's support community for insights from other users who might have faced similar issues. You can also send a support request directly from the BuildShip Dashboard if you suspect a deeper issue that you can't resolve【4:19†buildship-docs.json】.
If these suggestions do not resolve the issue, please try reaching out to BuildShip support for further assistance.
BuildShip AI Support
Hi @rodrigo1990_ could you please share this flow via in-app support?