Retool workflow unavailable on self-host

Workflows
1

When executing the Retool workflow via webhook, I am receiving the following response:

{"success":true,"workflow_run":{"id":"38c6c9fe-169b-427f-9a8b-fe73cfa50a64","workflow_id":"0be48fc9-8d81-4f82-99b4-a3662f65fae7","created_at":"2023-12-20T06:04:39.381Z","status":"SCHEDULING_FAILURE"}}

The status turns out to be SCHEDULING_FAILURE, and I cannot get the expected result, which leads to my question.

▼Background Previously
We self-hosted the version 3.10.2, but I detected information about a workflow bug.
Below is the error I encountered with 3.10.2:

{"workflowError":"Your workflow failed during execution.","runId":"2ca25faf-cebc-481b-85a1-4b9776b9da05","pluginId":"startTrigger","error":"request to https://null.undefined/api/workflow/runQueryForSandboxed failed, reason: getaddrinfo ENOTFOUND null.undefined"}

After the upgrade to 3.24.1, when I executed the workflow via a webhook again, the error message at the top occurred. The error did not resolve, so I had once unenrolled the workflow, which might be affecting this.

2

Hey @tomohiro.fukuya! Are you still facing issues here? That error generally means the backend pod can’t communicate with temporal frontend service.