I’m having the same exact problem. It worked two weeks ago and now I guess those timeouts are killing it. My log gives the same result:
I’ve tried to move the create csv from base64 into yet another (step 4) api workflow, but I don’t know if the same problem exists, where the CSV from JSON action doesn’t finish before the 4th workflow is scheduled with the file (parameter) therefore not being passed from step 3 to 4.
In fact the problem stays the same. The 4 step process works, but the same timeout kills it on the Create CSV from JSON step.
@prograds @julian.mcneill You are probably encountering the same issue where there is a timeout assembling the JSON. We do return an error message on the action if we encounter an error so you might look at creating a log in your database that stores the all the results of the Create CSV from JSON (SSA) including error, base64, etc.
Also, keep in mind that if it works on 250 in dev or a subset in live but not the full list of records, you may have data that is breaking your JSON. This would be exposed in the error message that is returned. In this case you’ll need to be sure you are using format as JSON-safe on any values that could possibly contain a breaking character such as a double quote or new line.
Otherwise, you will likely need to take the steps outlined in the following video to create your JSON first and then run the Create CSV workflow:
Thanks @eli
I am using the building-the-JSON strategy from your video and it works fine when it works. It works sometimes, and those are usually smaller exports.
But maybe it is in fact some JSON-breaking characters. Can we put format-as-JSON-safe on pretty much every text?
Don’t you think the solution here is to build the JSON and then schedule the next step for maybe 2 minutes later? Is there a way to do this, so that the base64 text file is save on the download and then it can be used in the email step? Right now I have this:
But because the csv file is there, this workflow wants to schedule this and send that file to the scheduled workflow, but the file doesn’t exist yet because the Create CSV from JSON step isn’t done yet.
Really appreciate the advice to solve this.
cheers
Fred
Hi @eli ,
I am using the method described in your video. I manage to create the final JSON and store it to the database.
Then I am passing it through the Create CSV from JSON (SSA) and I get the error Workflow error - Plugin action inputs too large, should be less than 6 MB
Final JSON is 160 000 lines and size of the file seems to be around 5-6MB.
The CSV that should be create would look like 5000 row with 30 col.
The error kinda make sense but I am not sure what’s the workaround here.
I’d prefer not to have to create 2 csv files.
Thanks,
for some reason the video and also the repost doesn’t work, it’s just a gif ;(
Hi @Oliver-wholegraintech were you ever able to figure this out with plugin inputs being too large for CSV Creator? I am getting the same error. “Plugin action inputs too large, should be less than 6 MB”.
Yeah this is a bubble limitation, I just created a CSV creation CloudFlare worker which I trigger via API and it returns a CSV, pretty nice and fast
1 Like
Thanks so much for the guidance @Oliver-wholegraintech
Same issue with the video