Get Credentials runs into a timeout on second call

Help Orchestrator
,
1

I have a process where the bot starts by opening IBM Notes, getting the credentials from the orchestrator and logs into notes.

Later in the process, the roboter needs to send mails via the “Send IBM Notes Mail Message”-activity. Since that activity requires the password, the roboter gets the credentials again.

It is all working fine until the bot tries to send a second email. Then the “Get Credentials”-activity runs into a timeout.

{
“message”: “Get Credential: Timeout für den Vorgang wurde überschritten.”,
“level”: “Error”,
“logType”: “Default”,
“timeStamp”: “10:24:24”,
“fileName”: “SendMail”,
“logF_BusinessProcessName”: “Framework”,
“processVersion”: “1.0.1”,
“jobId”: “ca6f60ee-6d27-41eb-b0e7-65c8edfbb39d”,
“robotName”: “Robo”,
“machineId”: 11,
“organizationUnitId”: 1
}

The strange thing is that in the dev environment (different terminal server and different orchestrator) eerything was working fine, even if the bot had to send 20 mails or more (and get the credentials 20 times or more).

How is that happening? Are there any settings in the orchestrator that could influence this behavior? Should I just get the credentials at the beginning of the process and pass them the the different workflows via arguments?

Thanks in advance
Simon

2

Should I just get the credentials at the beginning of the process and pass them to the different workflows via arguments?

If you are using the same credentials in the process, it is a good approach. In this way, you will reduce the time execution of the whole automation.