Getting "Internal Error running a block: Error: An internal server error occurred" error

💬 Workflows
1

I am trying to create my first workflow. We have dozens of apps and about 20 resources working in production. I am using an existing SQL resource but no matter the query I always get back the error:
{"data":null,"metadata":{},"error":"Internal Error running a block: Error: An internal server error occurred"}

I have seen this error reported a few times in different posts, but none of the suggestions fix my issue or are on the version I am on.
Retool Self-hosted
Version 3.114.10
Business Plan

Any advice?

Thanks in advance,
Steve

3

Hi @steve_melzer,

Apologies for the issue. Can you share a screenshot of the query? Or are you getting this error when testing the resource connection?

This is a not super descriptive error which is unfortunate. Are you able to check your workflow container logs to see if there is more details there on this issue?

4

image.png
image.png884×866 34.8 KB

5

Jack,
More details...
We are running Retool self-hosted. We are running on AWS. Here are the logs from the AWS console:


{
    "level": "info",
    "message": {
        "http": {
            "method": "POST",
            "url_base": "[retool.relaypayments.io](http://retool.relaypayments.io)",
            "url_path": "/api/workflow/a52f7646-0951-4382-a927-bca773acced2/runBlock?origin=frontend"
        },
        "type": "REQUEST_BEGIN"
    },
    "pid": 158,
    "requestId": "84d05587-e374-4329-a97c-c98cb4480683",
    "startTime": 1332562641.439335,
    "timestamp": "2025-08-07T17:26:20.403Z"
}
{
    "jobId": "44760709-2dcf-435d-bd73-7c578a105964",
    "level": "info",
    "message": "Running the block",
    "pid": 158,
    "requestId": "84d05587-e374-4329-a97c-c98cb4480683",
    "sequelizeCount": 12,
    "startTime": 1332562641.439335,
    "timestamp": "2025-08-07T17:26:20.439Z"
}
{
    "blockUuid": "d4025909-380b-4099-89f2-9c53bf303b95",
    "level": "info",
    "message": "Running workflow block",
    "timestamp": "2025-08-07T17:26:21.071Z",
    "workflowId": "a52f7646-0951-4382-a927-bca773acced2",
    "isSandboxLog": true
}
{
    "blockUuid": "d4025909-380b-4099-89f2-9c53bf303b95",
    "level": "info",
    "message": {
        "http": {
            "method": "POST",
            "url_path": "[https://null.undefined/api/workflow/runQueryForSandboxed](https://null.undefined/api/workflow/runQueryForSandboxed)"
        },
        "type": "CLIENT_REQUEST"
    },
    "requestId": "8e2e0283-08f6-4afe-9ab0-431885cce1e1",
    "timestamp": "2025-08-07T17:26:21.089Z",
    "workflowId": "a52f7646-0951-4382-a927-bca773acced2",
    "isSandboxLog": true
}

Notice the URL https://null.undefined/api/workflow/runQueryForSandboxed. I am not sure where this is coming from or what is misconfigured. Any help would be appreciated.

Thanks,
Steve

6

Hi @steve_melzer,

I was looking through internal docs and it seems that this error could happen if you don't set the workflow backend host.

Could you show me where that is set in your deployments config?

1 Like
7

I am so sorry to waste your time. It is a configuration issue on our end. This ticket can be closed.

Thanks,
Steve

8

@steve_melzer No worries at all!

Glad it was resolved. Feel free to share that part of the config it was in case there are other forum users with the same issue that are looking to remedy this!

9

A post was merged into an existing topic: Workflow block throws 413 error when referencing large data set