Hello Gabriella,
All of your guid session variables are the same because you are testing against an SF metasource instead of an IAM metasource. Indicium sets the guid session variable with the value of the use log session, as can be read here. For SF metasources, the use log session is always 1, because the SF does not track user sessions. So the resulting guid will always be 00000001-0000-0000-0000-000000000000 as well. You will get different guids per user and per user session if you test against IAM.
The guids for IAM metasources will always be xxxxxxxx-0000-0000-0000-000000000000, where xxxxxxxx is the hexadecimal representation of the use_log_session_id of that session.
select *
from use_log_session
So these guids are both predictable and easily derivable from data that is persistently stored in IAM, and therefore not suitable for the purpose mentioned in your previous topic.