Sleetza
Sleetza5mo ago

trouble exporting default function

Hey guys, This function I wrote works perfectly when I test it in test mode. When I run it as part of my workflow, it does not work. I think it has to do with the way I export the default function. Any pointers to what I am doing wrong? Code in attachment
Solution:
Hi @Clinton, the output too large, is not an issue, you can still return the value or view the value when you execute test, we are working on improving the UX around it.
Jump to solution
19 Replies
Gaurav Chadha
Gaurav Chadha5mo ago
Hi @Sleetza, could you please share the error message you get on running a test via workflow test?
Sleetza
Sleetza5mo ago
I am not getting an error
Gaurav Chadha
Gaurav Chadha5mo ago
Are the outputs different, if you could please elaborate of what is not working, as the export function looks fine.
Sleetza
Sleetza5mo ago
The enrich json function node replaces the value of 'omschrijving' for each 'werkervaring' object. It is working isolated, but not in the workflow:
No description
Sleetza
Sleetza5mo ago
It should replace '#####' and does that when I test the node isolated.
Sleetza
Sleetza5mo ago
This is the result when I test it isolated with the same inputs:
No description
Gaurav Chadha
Gaurav Chadha5mo ago
I would recommend adding logging.log and checking the values received.https://docs.buildship.com/logging
Logging – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
Sleetza
Sleetza5mo ago
You mean logging the 'text' and 'json' input variables when running the workflow?
Gaurav Chadha
Gaurav Chadha5mo ago
also logging in node logic to check the replace logic.
Sleetza
Sleetza5mo ago
Ok, interesting
No description
Sleetza
Sleetza5mo ago
Any clue what might be causing this? Am I hitting memory limits?
Sleetza
Sleetza5mo ago
Not sure whats happening, but now my entier workflow is gone:
No description
Gaurav Chadha
Gaurav Chadha5mo ago
It should be back working now, you can refresh the app.
Sleetza
Sleetza5mo ago
Its back, thanks. Any word yet on the input/output too large thing?
Gaurav Chadha
Gaurav Chadha5mo ago
okay, I missed that, it should not cause any issues, the value is simply too large to be displayed in log. But should not affect the execution.
Sleetza
Sleetza5mo ago
Right So how can I figure out why it does only work isolated but not in the work flow?
Clinton
Clinton3mo ago
This is also an issue for me using an API call node. When I test in BuildShip all works fine but when I test on production I get "output too large". This is with the same inputs on both test and prod.
AI Support
AI Support3mo ago
For issues related to "output too large" in BuildShip, it is recommended to review the workflow and optimize the data handling. Here are a few suggestions to consider: 1. Check Output Size Limits: Ensure that the output size does not exceed the limits set by BuildShip. You may need to paginate the data or reduce the amount of data being processed. 2. Optimize Data Handling: Consider breaking down the data into smaller chunks if possible. This can prevent the output from becoming too large. 3. Logging and Debugging: Use the logging feature in BuildShip to monitor and understand the flow of your workflow. This can help identify where the output size is becoming too large. For more detailed guidance, you can refer to the BuildShip documentation on logging: BuildShip Logging Documentation If the issue persists, it is recommended to submit a request via the in-app support button for further assistance.
Logging – BuildShip
A unified resource to start building your backend with low-code. Dive into triggers, nodes, and step-by-step guidance to jumpstart your workflow creation.
Solution
Gaurav Chadha
Gaurav Chadha2mo ago
Hi @Clinton, the output too large, is not an issue, you can still return the value or view the value when you execute test, we are working on improving the UX around it.