Skip to content

Conversation

lovey89
Copy link

@lovey89 lovey89 commented Aug 6, 2025

Short description of the problem

When workflows.enabled is set to false, the code executor will not be deployed. The CODE_EXECUTOR_INGRESS_DOMAIN environment variable will still be added to backend deployment and prevent it from starting as the backend would try to connect to the executor during start up.

You see the following error messages during boot:

Code executor is configured via CODE_EXECUTOR_INGRESS_DOMAIN but not available.
Could not detect healthy Code Executor. To ignore failures of this check on startup, set IGNORE_CODE_EXECUTOR_STARTUP_CHECK=true.

You can see the problem on the current main branch by running:

helm template \
    --set config.encryptionKey=key \
    --set image.tag=3.148.26-stable \
    --set workflows.enabled=false \
    -n retool retool charts/retool | less

In the output you can see that CODE_EXECUTOR_INGRESS_DOMAIN is set for the retool backend deployment, but there is no retool-code-executor service.

Solution

With this change, the CODE_EXECUTOR_INGRESS_DOMAIN environment variable will only be added to the backend deployment if workflows are enabled

…abled

When workflows.enabled is set to false, the code executor will not be
deployed. The CODE_EXECUTOR_INGRESS_DOMAIN environment variable would
still be added to backend deployment and prevent it from starting as the
backend would try to connect to the executor on start up.

With this change, the CODE_EXECUTOR_INGRESS_DOMAIN environment variable
will only be added to the backend deployment if workflows are enabled.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant