Retool Workflow just shows 'Internal Server Error' for everything and anything on specific branch

  1. My goal: Get my protected workflow back running normally
  2. Issue:
    I have a protected workflow that connects to s3 and a snowflake db. I am on a specific development branch and this branch with the workflow now is always showing: Internal server error. I’m concerned that some process behind the scenes in the Retool Ecosystem that is blocking it.
  3. Steps I've taken to troubleshoot:
    Things I’ve tried:
    • I’ve changed branches and it works fine and I don’t run into this error.
    • I’ve looked into seeing if there was anything I added to the workflow that could have resulted in this error, but it just infinitely loads when seeing changes.
    • I’ve tried to delete blocks from the workflow and add them back; however, it brings back the blocks and shows an Internal server error Error saving workflow.
    • I’ve tried to run my s3 block with an arbitrary s3 key, that fails with: {"data":null,"metadata":{},"error":"Internal Error running a block: Internal server error"}.
  4. Additional info: (Cloud or Self-hosted, Screenshots)
    cloud-hosted

1 Like

@Darren could you help take a look into this issue? Is this something that other people have been seeing?

Hey @brpark - I don't think there is any widespread outage on our end, but I'm happy to help you dig into this. Can you confirm the workflow ID and relevant branch name?

Thanks @Darren for the quick reply!

I just ran it again today for a Retool app, and I saw the same “Interval Server Error" messages. However, when I go to the test branch I’m working with there are no “workflow runs” showing. It’s just empty.

I can show you more information on a screenshare.

Sounds good! Feel free to send any sensitive info via DM or to join tomorrow's Office Hours. :+1:

What happens if you create a new branch? Some of my initial research seems to suggest that there's an issue with the source-control state of the workflow as a whole. :thinking: Did you try to unprotect it at some point?