Enfocus Community

Sad story. It only works when the parameters come back fast enough. I penetrated it with ~20 switch jobs sequentially (not even parallel) and all those jobs had the same parameters being read from a database. Don't get me wrong, but 20 test jobs is not even much, this would definitely happen in prod...

I highly appreciate your help, Thomas. When I try your code, I get: Argument of type '(value: unknown) => void' is not assignable to parameter of type 'number'. because the setTimeout returns void and something else is expected? I was eager enough to "just remove" the _resolve_ keyword/par...

We experience this even more often. Using variables from "a Database Connection" (via the Database Connection Module) as parameters for scripts seems to be broken. I don't know if this is something that only we experience? If anybody else can confirm this "behavior", this might b...

The SQL SELECT works within the Switch Flow and the # hashtags are just placeholders as I wrote:

(the hashtags are placeholders for privacy reasons, this part is just an example and works 100%)

We use a SwitchScript to save values in private data fields of the job and this script works perfectly well as a legacy script. We now rewrote it as a NodeJS SwitchScript and it also works like a charm, but NOT when a parameter value for the script comes from a variable that fetches a value from a D...