[QUESTION] }bedrock.process.multithread'

[matteolorini]

Describe what you are trying to do with Bedrock5
I’m trying to understand the multithreaded behavior of the TI process

Describe what's not working the way you expect
Didn't get the expected result? Describe:

I tried using the TI to execute a process while setting pMaxThreads to 5, 10, or even 0, but when I check the active sessions, I always see only two processes running and the others remaining in a waiting state.

Code Example
myTaskList= '
[
{
"process": "myProcessLoadCube",
"parameters": {
"pLocation": "US",
"pPeriod": "2025-07",
"pPeriod2": "2025-08"
}
},
{
"process": "myProcessLoadCube",
"parameters": {
"pLocation": "CA",
"pPeriod": "2025-09",
"pPeriod2": "2025-10"
}
},
{
"process": "myProcessLoadCube",
"parameters": {
"pLocation": "GB",
"pPeriod": "2025-11",
"pPeriod2": "2025-12"
}
},
{
"process": "myProcessLoadCube",
"parameters": {
"pLocation": "DE",
"pPeriod": "2026-01",
"pPeriod2": "2026-02"
}
}
]
';

ExecuteProcess( '}bedrock.process.multithread', 'pTaskList', myTaskList, 'pMaxThreads', 0);

Environment:

• Bedrock5 Version: [e.g. 1.0.0]
• TM1 Server Version: [e.g. 12.5.1] on-prem
• HA Settings: [e.g. number of replicas]
• Installation type: [it is V12 On-Prem]

Additional context
If you encounter an error, please add the error message and the stack trace:

[matteolorini]

My question is: Is this the expected behavior? When I write a simple TI process with four RunProcess calls, I can see all four threads running simultaneously in the PAW active sessions.

[bdunleavy22]

Hi @matteolorini , that is definitely not the expected behavior. I'll mark this as an issue, look into it, get back to you on what I find!

[bdunleavy22]

I tried to recreate the issue you were facing by making a dummy TI "myProcessLoadCube" which just sleeps for 10s, and has the 3 parameters you passed. I ran }bedrock.process.multithread in the same way that you did, and it ran as expected.

However, I did this test on PAaaS. It will take some time, but I will procure a v12 on-prem instance to further try to recreate the issue