Output too large on API call node
I have an API call node that works fine in test mode but breaks in production with am "Output too large" message. Both the test and production are using the same inputs.
The output of the node is used in a loop node further on in the workflow.
Solution:Jump to 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.
2 Replies
The issue you are encountering with the "Output too large" message in production might be due to the size of the data being processed. Here are a few suggestions to resolve this:
1. Paginate the API Response: If the API supports pagination, you can modify your query to fetch smaller chunks of data in multiple requests instead of a single large response.
2. Filter the Data: Ensure that you are only fetching the necessary data from the API. You can use query parameters to limit the fields and data points returned by the API.
3. Process Data in Chunks: Instead of processing a large dataset in one go, break it down into smaller chunks and process each chunk individually.
4. Increase Node Output Size Limit: If possible, check if there is an option to increase the output size limit for the node in the BuildShip settings.
For further assistance, you can refer to the BuildShip documentation or submit your issue via the in-app support button for more detailed guidance.
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.