I don't know why that's happening, but I believe it occurs when something goes wrong with determining whether the current component (object/process) is authorized to retrieve the credential. I think I've seen that error before I don't remember getting it repeatedly. Does this always happen from the object?
One thing to check (though it normally should give you a different authorization error) is whether the credential you're trying to retrieve is set to Access Rights > Processes > All Processes or not. If it's not set to All Processes then the object will not be able to retrieve credentials since you cannot grant access directly to an object. The only way to retrieve credentials from an object in DEBUG mode is one of two ways: (1) step into the object from a process that does have access to the credential or (2) set the credential's access rights to All Processes so that there is no restriction at the process/object level.
Because object's get their authorization for credentials from the calling process is the reason I'm explaining all this. Your error would indicate that Blue Prism could not determine whether the session (that the object is running under) has access to the credential. So, I'm not sure if Blue Prism incorrectly generated a session ID or if the Credential action just failed to retrieve the session ID. Seems more likely to be the second. Either way, is this happening in debug mode or also from control room?
------------------------------
Dave Morris
3Ci @ Southern Company
Atlanta, GA
------------------------------
Dave Morris, 3Ci at Southern Company
