Cron trigger - Fails
My workflow starts with a cron trigger. the test is successful, but when i want to ship, i have an error : Failed at managing trigger node. Error: 14 UNAVAILABLE: 502:Bad Gateway
any idea how to fix that ?
Solution:Jump to solution
Hi @GetInference on checking the workflows you shared via support, all your everyday cron triggers are already shipped. Are you still facing this issue?
4 Replies
AI Support Bot Information
<@398973549018087425> 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
This error indicates that there is an issue with the connection or the server, resulting in a "502: Bad Gateway" error. This typically means that the server is temporarily overloaded or undergoing maintenance. Here are a few steps you can take to resolve this:
1. Check Server Status: Ensure that the BuildShip servers are operational and not undergoing maintenance. You can check this on the BuildShip status page or contact support.
2. Retry Shipping: Sometimes, simply retrying to ship the workflow after a brief wait can resolve the issue. There might have been a transient issue causing the error. 3. Network Issues: Verify that there are no network issues on your end that might be causing the connection problem. Ensure your internet connection is stable. 4. Contact Support: If the issue persists, you may need to contact BuildShip support for further assistance. Provide them with the error message and any relevant details about your workflow. You can also try the BuildShip in-app support or send an email to
2. Retry Shipping: Sometimes, simply retrying to ship the workflow after a brief wait can resolve the issue. There might have been a transient issue causing the error. 3. Network Issues: Verify that there are no network issues on your end that might be causing the connection problem. Ensure your internet connection is stable. 4. Contact Support: If the issue persists, you may need to contact BuildShip support for further assistance. Provide them with the error message and any relevant details about your workflow. You can also try the BuildShip in-app support or send an email to
hello@buildship.com for urgent issues.
BuildShip AI Support
Solution
Hi @GetInference on checking the workflows you shared via support, all your everyday cron triggers are already shipped. Are you still facing this issue?
not anymore, thank you @Gaurav Chadha