Nilvees
Nilvees3w ago

Internal error, workflow schema is invalid.

Failed: Internal error, workflow schema is invalid. Please contact support. Error in following nodes: - name 1 XXX - name 2 XXX - name 3 XXX
Hi, I have an issue, it's related to a business plan for a very important client. I’d really appreciate it if you could contact me privately. The problem is affecting several of workflows, although everything was working fine before.
6 Replies
AI Support
AI Support3w ago
AI Support Bot Information
<@459421296762028045> 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 Support3w ago
AI Response
I understand the urgency of the issue, especially given its importance to your client. However, I'm unable to contact you privately. I recommend sending a support request through the in-app support feature in BuildShip for immediate assistance. They will be able to investigate and help resolve the problem with your workflows.
BuildShip AI Support
Nilvees
NilveesOP3w ago
No description
Gaurav Chadha
Gaurav Chadha3w ago
Hi @Nilvees This should be fixed now, you can refresh the app and ship again
Nilvees
NilveesOP3w ago
Error generating BuildShipFile instance for input timestamp: Invalid file instantiator value. Pass in a 'type' property when calling this function.
Error generating BuildShipFile instance for input timestamp: Invalid file instantiator value. Pass in a 'type' property when calling this function.
I did a ship, but the issue still occurs when the CRON triggers the workflow. @Gaurav Chadha
Gaurav Chadha
Gaurav Chadha3w ago
can you delete and add the trigger again, then ship and share the screenshot of the new error?

Did you find this page helpful?