Self hosted workflows wont start

Im using the self hosted retool using the docker-compose with temporal added from https://github.com/tryretool/retool-onpremise/blob/master/docker-compose-workflows.yml

However I can't get the workflows container to start. I see this error:

node:internal/modules/cjs/loader:933
  const err = new Error(message);
              ^

Error: Cannot find module './temporal/workflowsExecutor/workflowsExecutor-workflows-bundle.js'
Require stack:
- /snapshot/retool_development/backend/transpiled/temporal/workflowsExecutor/onpremWorker.js
- /snapshot/retool_development/backend/transpiled/temporal/workflowsExecutor/main.js
- /snapshot/retool_development/backend/transpiled/main.js
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)
    at Function._resolveFilename (pkg/prelude/bootstrap.js:1912:46)
    at Function.resolve (node:internal/modules/cjs/helpers:108:19)
    at startTemporalWorker (/snapshot/retool_development/backend/transpiled/temporal/workflowsExecutor/onpremWorker.js)
    at Object.main (/snapshot/retool_development/backend/transpiled/temporal/workflowsExecutor/main.js)
    at processTicksAndRejections (node:internal/process/task_queues:96:5) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/snapshot/retool_development/backend/transpiled/temporal/workflowsExecutor/onpremWorker.js',
    '/snapshot/retool_development/backend/transpiled/temporal/workflowsExecutor/main.js',
    '/snapshot/retool_development/backend/transpiled/main.js'
  ]
}

How can I fix this?

Also is there a way I can use my own temporal from temporal cloud?

Hey @tpbs!

What version of Retool are you using? It's possible that this is related to a packaging issue from version 3.4.2 that the dev team was looking into this morning. A fix was recently pushed with 3.4.3 - can you try upgrading and let me know if that solves the problem?

Thanks @Kabirdas

I will try using the latest version.

Also is there a way I can use my own temporal cloud (a way to deal with the certificates)?

Apologies for the late reply here @tpbs!

If you're looking to deal with certificates there are a few environment variables that can be set:

WORKFLOW_TEMPORAL_TLS_ENABLED
WORKFLOW_TEMPORAL_TLS_CRT
WORKFLOW_TEMPORAL_TLS_KEY

These will be documented as well! Can you let me know for now if setting those solves your certificate issues?

Thanks @Kabirdas. With WORKFLOW_TEMPORAL_TLS_CRT and WORKFLOW_TEMPORAL_TLS_KEY do i pass the raw certificate string in, or is it a file path?

Ah good question, pass in the raw certificate string.

@Kabirdas im having a similar issue to this one when i pass the raw certificate string

:thinking: and both strings base64-encoded? Are you seeing a PrivateKeyParseError as well?