Ship Flow - Failed
What does this message mean - Failed: Value for argument "data" is not a valid Firestore document. Input object is deeper than 20 levels or contains a cycle. ?
Also, would it be possible to get an upgrade to the editor so that when working on larger workflows I can at least see the structure?
11 Replies
Processing...
🤖 Assembling the pieces of the puzzle. 🧩 this might take a couple of minutes... beep boop
Actually can I raise this as a bug, I went over some particulars like aligning some of the new inputs for the expansion I had missed, now the workflow will ship, but only stays shipped for about 2 seconds. Then when I when I have gone to test it, the Telegram bot that was previously working before the expansion, now only sends "undefined" no idea why, the message doesn't even reach the workflow to be able to debug it.
843685 on in app support
Hi @Chris Wright | Because You Can we're are working on adding a fix for the large workflows, thanks for sharing via support.
On checking your workflow, it is exceeding the Firestore limit, in simple terms, the workflow is very large, if you delete one node from your switch, it will then deploy. Instead, I would recommend you split your workflow and use the Execute BuildShip Workflow node and call some part of your via another workflow, you can refer to these docs for more info on how to use the BuildShip execute workflow node - https://docs.buildship.com/core-nodes/execute-workflow.
Ok Gaurav, appreciate you taking a look
But how do I fix the Telegram bot again, why do they break so easily, all I'm getting is these "undefined" failed workflows, it was working perfectly until that point.
Can you reship and log? The trigger data?
I have unpaused the workflow and instantly I'm getting failed attempts coming through, I did add a logging node inside the inputs and reshipped, but the failed attempts are just "undefined" they don't even make it to the inputs.
oh and I can't delete the Telegram trigger either
So I have managed to copy nodes from the affected flow, recreate it in a new flow, set up a new Telegram bot, align all send message nodes with the new TG auth, but then I've sent a message to it and i'm trying to "get data" to connect the inputs and it says that there are no messages when there are. I manage to ship the workflow anyway, but I am getting brand new and repeated Failed - "undefined" for this new Telegram workflow.
Is this a duplicated flow? I'll test it on my end can you share the updated flow via in-app, add a link to this conversation in the support message.
It is duplicated nodes in a brand new flow. I'll share it.
Hey @Chris Wright | Because You Can , it seems your botfather key is expired, you'll have to generate a new one and then try.
I tested it with my botFather key on a new Telegram trigger, and it is receiving the webhook correctly
No I don't understand it, it was a new bot, I'll try another new bot, maybe they'll soon give me shares in Telegram because I have so many bots 😂