Workflow not updating and only working on "test"
Hello @Gaurav Chadha I've just sent an in app support request. It seems like one of my workflows is broken and only works on test it but not production. This is really urgent and it would be good if you can take a look. I also added a log node and it seems like the workflow is not being updated because the log node is just being ignored.
11 Replies
AI Support Bot Information
<@1227983829856157809> 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
Unfortunately, there isn't specific information in the provided documents that addresses the issue of a workflow working in test mode but not in production, or why a log node might be ignored. This might be a unique situation that requires in-depth technical support. Please continue with the in-app support request, as that is the best way to address urgent technical issues like this【4:1†buildship-docs.json】. If you need any further information or assistance on setting up and troubleshooting workflows, you may also refer to the BuildShip Documentation.
BuildShip AI Support
Hi @Brian I've added another log node on your flow, and deployed.
Can you make a prod request? I just want to ensure if the deployment is updated or not.
I tested it once and I could not see the log node being run in the logs. Furthermore it also failed to execute again. Then I tried running it with a "Re-Test" and now this happens
@BuildShip Need support for this asap
Duplicating the flow turns into an empty workflow
added a fix it, it should load now,
We are working on a permanent fix for this cc @Deepanshu
Okay I can see the workflow again
Hmmm okay now I have this "NaN is not allowed" error again. This happens always when I do a "Re-Test". Are you working on a permanent fix for this right now? We have a client that needs to have a working app in a couple of hours.
Puhh..okay luckily I duplicated the workflow after you made the temporary fix. The duplicated workflow works as expected. Seems like something is really internally broken with the original workflow.
@Brian can you provide some details on the broken workflow?
did you create it from scratch or from some template or duplicated ?
I just duplicated it when that "NaN is not allowed" was temporarily fixed.
I will use the duplicated workflow now for safety reasons. Maybe you can give us an insight later on why the original workflow did not update anymore?
So this issue still persists also in my other workflows. I just sent out another in app support request: #869232
I hope you can find out the issue, otherwise I cannot trust that any of my workflows run on the latest shipment.
@Gaurav Chadha @Deepanshu Here I have another workflow that does not seem to update: Support ticket #859565
Hi @Brian thanks for sharing.
could you please try this?
- clear browser cache or try with incognito.
- redeploy/ship that workflow.
- ensure that the logging panel is closed. Do a hard refresh of browser.
- then make a new prod request.
if this doesn't work, we can get on a call
I think it kinda worked...? But I still see these cryptic node IDs. So is this 100% a browser issue when shipping?