Truncated payload - where is stored full response body ?

[miro2]

Hi,

In which table can I find the full payload I received in the step output? The payload is truncated, but somewhere the payload should be stored to get the full data.

[Tony Chatfield1]

Hi, unfortunately partial screenshots do not provide any clear details of your configuration.
Is Step Output Data a custom or OOB variable? which table does it relate to, how is it configured, what function\process populate sit?
The most common cause of truncation is target field sizing.

[poyntzj]

I am going to guess - as I have an identical problem - that this is an OOB action.

In my case I am looking to retrieve the contacts details by using the OOB Wrike "Look up Contacts" action.

It runs, but is truncated (roughly 172000 bytes on each run)

Way below the default 5MB limit - but I have set to 10MB

I have increased the timeout - just incase it was that (doubted it)

I have now managed to check the same API call in postman, and that is returning the full payload, so I want to see what the underling data is when stored in the relevant table, and not in the designer (as I have seen many a web page truncate when the underlying data is good)

so, as miro2 is asking (and perhaps they are using the miro spoke?), I want to find the actual underlying data in whatever table to see what is going on.

[miro2]

Hi @poyntzj 

In my custom REST action, I added a logging step to capture the Response Body. I was able to see the entire payload in the log table, which was essential for my testing purposes. However, I couldn't identify where it was stored. Even if the response body seems truncated, the full payload is indeed received.

[Tony Chatfield1]

Hi, a response REST message\body will not normally be 'stored' anywhere, rather it is received, processed and then ceases to exist; but this may be down to your configuration or the functionality you are utilizing.