Access Request Provisioning Workflow Not Triggering Final Email - "internalName cannot be null" Error

We’re facing an issue where the Access Request Provisioning Workflow fails to trigger the final email notification after the manual task is completed by the source owner. The workflow is configured to send an email to both the requestor and the recipient, but it isn’t running as expected.

Instead, we encounter the following error:

“An unexpected error occurred: internalName cannot be null.”

Has anyone experienced this issue before? Are there any known workarounds or solutions for ensuring the workflow executes successfully and sends the final email? Any insights would be greatly appreciated!

1 Like

Hi @swatisharmaaccent

Welcome back to sailpoint community. Do not think i can help much with the information provided, but you may want to see the trigger input from workflow execution logs and then see if the required details were present in the workflow. If possible, i would also suggest you to test the workflow with the same input and then see where it fails.

I hope this helps.

Regards
Vikas.

I am facing the same error from past 3 days which was working fine earlier.. My requirement is to trigger a workflow once the Manual Action item is marked as completed. Raised a case with SailPoint

I’m also facing this issue and am facing major impacts from this. @Prashant_Rathipelli please let me know what you hear from your ticket :slight_smile:

We are facing the same issue since 21st of March
An unexpected error occurred: internalName cannot be null

Thank you for considering this issue, please let us know if you will get any workaround from saipoint vendor on this issue.

The issue is now fixed. The workflow is getting triggered successfully. You can test it now. At the moment there is no RCA but SailPoint confirmed that there were some changes made on the Triggers which caused this issue and change was reverted back yesterday which fixed the error