Some logs show detailed steps under "Blocks" -- for instance, the start trigger and other steps, and I can click into the inputs / data / JSON / logs, but others do not and just show logs.
Shows detail:
Does not show detail:
Retool cloud. Would also be good if there was a way to export logs or store them in Retool database, but not directly related to the issue.
I also have this issue too: Especially with dealing with workflow failures. It's not very helpful as I don't see where my workflow has failed.
I am seeing an infinite loading error for my failed workflow
Hello @npr and @brpark, thanks for your report! Could you let us know if your workflow is using an S3 resource?
Also, could you please share the Workflow Run ID from the most recent time this issue occurred? That will help us investigate more accurately.
Appreciate your help! 
Hi @ChiEn ,
Yes, I was/am currently using an S3 resource. Here's the run ID for one that errored. Here's the
workflow id: d989639e-34c6-4fa7-955e-88a460bf1683
runId=0197f6e8-c927-76de-8bfe-dc28737380b3
I believe we were able to solve this issue by moving our s3 resource in a function within a workflow. However, I was more curious in how I could see in the logs what exactly was erroring or which block was having issues. Is this possible?
Hi @ChiEn , thanks - a recent run ID: 01982c8c-28a1-7fe3-bcdb-17353a5699d1 on 2025-07-21 06:33 ; and yes, it uses S3!
Thanks for sharing your run IDs @brpark and @npr! For performance reasons, we skip loading logs from S3 blocks when the total size exceeds 20MB. This helps ensure things run smoothly and avoids any potential crashes on your side.
The UI team is working on making this behavior clearer by showing a message when log data is truncated, so it’s easier to understand what’s happening.
Let us know if there’s anything else we can do to help, and thanks again for understanding! 
