Workflow Failing Without Errors or Explanation

My goal:
To run a Retool Workflow on a schedule without intermittent failures.

Issue:
The workflow fails every 1–2 days. In the run history, it just shows Status: "Failure" with 0 errors and no explanation. Some blocks are not executed at all, and this same pattern happens every time it fails.
I've attached a screenshot of the run history to show exactly what I’m seeing.

Steps I've taken:

  • Checked error logs (no errors shown)
  • Reviewed workflow logic and block dependencies
  • Verified triggers and conditions are correctly set

I also found this topic from another user who seems to be experiencing a similar issue.
Would appreciate any insights or suggestions from the community or Retool team on how to debug this further.

Thanks!

I have the same issue! So weird, when I call a workflow from another workflow I get the message

{"workflowError":"Your workflow failed during execution."}

But checking the logs on the calling workflow it keeps giving me loading spinner. with no logging output whatsoever..

Hello! I have two similar issues:

  1. Workflow stops processing and marked as failed with any error.

  2. Workflow fails without any logs or reason.

The more workflows run in parallel, the more likely it is that the behaviour occurs.
I'm using Retool Self-hosted. Is there anything about the deployment I need to change?

Thanks in advance!

Hi everyone,

@Adnan_Khalil1 and @devopser, are either of you self hosting like @lucianholt is?

For self hosted there may be some additional logs from the workflows container that we could look at to check for clues on what could be going wrong.

Apologies for the issue. Let me touch base with the workflows team and check with them on best steps to trouble shoot what could be causing these to fail :thinking:

Could you share some more details on your self-hosted set up?

How are you deployed, what versions are you on? Are they able to send workflows container logs?

For users on the cloud, if you can share workflow ids and workflow run ids we can check our logs to see if there are more details we can find to clear things up.

We run the self-hosted setup with the provided docker compose file, a self-hosted temporal and an external PostgreSQL database. It's running a VPS with 14 cores and 36 GB of memory. We are running edge version 3.207.0.

1 Like

Thank you so much for sharing these details! Very helpful @fibis

Can you share with me a dump of their workflows container logs? Would also confirm if they mean self managed or local cluster.

I also just want to confirm weather you meant self managed or local cluster :sweat_smile: As the answer to that will determine which steps from the set up docs here I would recommend for you to double check that you have set up correctly.

I do not use a self-hosted instance. It keeps giving me the loading spinner when checking the logs.

Hi @Jack_T I have here some looks for you. I see here some heartbeat errors and also network issues. The CPU and memory usage is looking good during the run: workflows-worker-1 | 2025-07-03T20:09:11.000722959Z {"activityId":"2","activity - Pastebin.com

We are using a Temporal local cluster.

Hi folks, I have been working with the workflows team to try to investigate what could be causing this.

Is the issue still ongoing?

For testing purposes, if you can add a Response Block to the end the the workflow, that may be able to capture an error message for a failing workflow to give us more details.