Hello Clive,

By saying you have two sets of users that perform completely separate transactions, did you mean separate user paths ? Or did you mean these users perform separate transactions in the same user path ?

Best Regards,
Fousseyni B.

The users are following 2 separate user paths.
They sit in separate populations.

Hello Clive,

Assuming your virtual users are consuming data from different file variables, your data set may not be appropriate. You can verify that by manually login in the application with those users who failed to connect to the right application.

Best Regards,
Fousseyni B.

Don't think you've got what's happening.
The authentication method used for the application requires NeoLoad to have the user credentials (id/password) in the server definition.
So there's two server definitions, say A and B. The host definition is the same just the credentials are different.
There are 2 separate user paths, one for each set of users. The user paths work fine for the users they are meant to do. In the user paths, each call has the server definition included.
What happens is intermittently when running a check user path or a test, the scripts pick up an entry from the wrong datapool of users. This causes a complete meltdown.
I need to control the number of users running each user path so cannot just detect which user gets signed on and executing suitable transactions.
This seems to be a bug in NeoLoad or is there another way to address getting two different sets of users to point at the same host URL?.