While the activity “Set Credential” has the property “Continue on error” and the activity “Get Credential” lacks this property. It also lacks “Result” property of “Get Secure Credentials” so to handle missing credentila asset require enclosing “Get Credential” activity in Try/Catch.
It would be nice if “Continue on error” propperty is used consistently for all activities.
My assumption is that the Get Credential activity in UiPath lacks a “Continue on Error” property because it is designed to handle credentials securely and reliably. If there’s an issue retrieving credentials, it usually indicates a critical error with the credential store or the retrieval process. Handling this type of error directly is crucial for maintaining security and ensuring that the automation does not proceed with potentially incorrect or missing credentials.
If you encounter issues with credential retrieval, consider enclosing the Get Credential activity in a Try Catch block. This approach allows you to manage errors more gracefully by logging appropriate messages or implementing fallback logic if needed.
Hi,
I ended-up with this approach indeed. As workaround I created a custom activity that simulates the functionality of “Get Secure Credentials” including the “Result” property.