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

enrich_json_object_with_full_werkomschrijving_extracted_from_line_number_prepended_string.txt2.29KB

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

SSleetza Hey guys, This function I wrote works perfectly when I test it in test mode. Whe...

Gaurav Chadha•5/13/24, 6:13 PM

Hi @Sleetza, could you please share the error message you get on running a test via workflow test?

SleetzaOP•5/13/24, 6:13 PM

I am not getting an error

Gaurav Chadha•5/13/24, 6:14 PM

Are the outputs different, if you could please elaborate of what is not working, as the export function looks fine.

SleetzaOP•5/13/24, 6:15 PM

The enrich json function node replaces the value of 'omschrijving' for each 'werkervaring' object. It is working isolated, but not in the workflow:

SleetzaOP•5/13/24, 6:15 PM

It should replace '#####' and does that when I test the node isolated.

SleetzaOP•5/13/24, 6:17 PM

This is the result when I test it isolated with the same inputs:

SSleetza The enrich json function node replaces the value of 'omschrijving' for each 'wer...

Gaurav Chadha•5/13/24, 6:17 PM

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.

SleetzaOP•5/13/24, 6:18 PM

You mean logging the 'text' and 'json' input variables when running the workflow?

Gaurav Chadha•5/13/24, 6:19 PM

also logging in node logic to check the replace logic.

SleetzaOP•5/13/24, 6:22 PM

Ok, interesting

SleetzaOP•5/13/24, 6:22 PM

Any clue what might be causing this?

SleetzaOP•5/13/24, 6:37 PM

Am I hitting memory limits?

SleetzaOP•5/13/24, 6:44 PM

Not sure whats happening, but now my entier workflow is gone:

SSleetza Not sure whats happening, but now my entier workflow is gone:

Gaurav Chadha•5/13/24, 6:55 PM

It should be back working now, you can refresh the app.

SleetzaOP•5/13/24, 7:07 PM

Its back, thanks. Any word yet on the input/output too large thing?

SSleetza Ok, interesting

Gaurav Chadha•5/13/24, 7:08 PM

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.

SleetzaOP•5/13/24, 7:09 PM

Right

SleetzaOP•5/13/24, 7:10 PM

So how can I figure out why it does only work isolated but not in the work flow?

Clinton•8/1/24, 12:29 PM

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.

CClinton This is also an issue for me using an API call node. When I test in BuildShip al...

AI Support•8/1/24, 12:29 PM

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:

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.
Optimize Data Handling: Consider breaking down the data into smaller chunks if possible. This can prevent the output from becoming too large.
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•8/6/24, 6:44 PM

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.