Error Using DocuSign Spoke After Xanadu Upgrade from Washington

[Bsublett]

Has anyone experienced an access error pertaining to the DocuSign Spoke in a flow after the Xanadu upgrade?

When our flow executes we get the following error: "Error: Cannot find function buildVerificationPayload in object"

referencing DocusignUtils(). I have seen in the logs an access denied error that I have attached. The flow and sub flow run as the system user. Any insights would be appreciated. This was working before the upgrade and we have also tried updating the DocuSign spoke in another instance with the same error as a result.  

Thank you.

[jcmings]

Any chance the function buildVerificationPayload was customized and the change was reverted during the upgrade? Check your upgrade history and see what was skipped, reverted, and maintained.

Also you may need to check for cross scope access. Based on your screenshot it doesn't look like the Docusign application has access to your record anymore. This could also be something impacted by the upgrade.

[Bsublett]

Thank you for the suggestion. I am looking into that now. 

[Bsublett · Accepted solution]

Turns out someone had edited the DocuSignUtils obj that is part of Docusign eSignature Spoke.

Returned it to base and got past that part.