How to handle @@DGB_TRUNCATED@@

Understand the use of the @@DGB_TRUNCATED@@ placeholder to optimize memory and handle large volume JSON responses.

In the Digibee Integration Platform, you may encounter the term @@DGB_TRUNCATED@@ when working with connectors that return long JSON responses. This placeholder is a mechanism designed to optimize memory usage by truncating the response and is used when a JSON response exceeds a certain length.

While it may seem like an obstacle at first, understanding its purpose and how to use it can streamline your workflow and ensure accurate data processing.

What is @@DGB_TRUNCATED@@?

The term @@DGB_TRUNCATED@@ is used by Digibee to indicate that the payload recorded in the log messages has been truncated. This happens when the payload is larger than 320kb. In these cases, the pipeline is executed normally, but the payload is logged in truncated form.

Why does @@DGB_TRUNCATED@@ occur?

The main reason for using @@DGB_TRUNCATED@@ is to save memory. By truncating long JSON responses, the Digibee Integration Platform can efficiently manage memory usage, especially in scenarios where large payloads are processed.

How to handle @@DGB_TRUNCATED@@?

If you find @@DGB_TRUNCATED@@ in your workflow logs or outputs, it’s important to understand that this is not the original JSON response. To view the full JSON data, you have two alternatives:

• Manually convert it by removing the @@DGB_TRUNCATED@@ placeholder and any extra characters introduced during truncation. In particular, make sure that you convert single quotation marks (') to double quotation marks (").

• If you are working with the Execution panel, you can place the connector that returns the truncated JSON at the end of your workflow. This way, the Digibee Integration Platform recognizes that you need the full JSON response and sends it correctly without truncation.