Flow designer error: Unable to load connection with alias ID for DocuSign
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2025 06:33 PM
We are trying to use DocuSign spokes in flow designer and we are encountering "Unable to load connection with alias ID" error. The flow already runs as system user. Unable to verify what connection alias record it is using since in the flow execution logs it shows empty target.
Unable to load connection with alias ID: <a href="/sys_alias.do?sys_id=" target="blank">Open Connection Alias</a>Any of you have same experience and what did you do to fix this?
Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Good Morning,
Did you ever get this resolved? I am having the same problem.
I have it working but it looks to be related to the DocuSign webhook when other e-signutres have been requested outside of ServiceNow which is triggering the DocuSign Webhook Sample Subflow and causing the same error.
Kind Regards
Ashley
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi Ashely,
I forgot the exact fix I made but instead of using the Out of the box flow provided for DocuSign, I instead created a copy of it and troubleshooted the error then update my copied flow based on the error encountered.
If I remember correctly I hard coded something a value that was missing or something...
Hope that is helpful or understandable 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Good morning,
Thank you for your reply.
I ended up logging an HI ticket with ServiceNow, and we managed to get to the bottom of the issue. While one option is to clone the Flow Action and hard-code the alias — which I assume is what you've done — I want to keep everything OOB. To resolve this, we’re going to create a new DocuSign account dedicated to this integration so no additional webhooks are generated.
For a bit of context: external e-signatures are being generated, which is triggering all the DocuSign webhooks. These are sending the envelope payload to our instance, which then searches the DocuSign Envelope table. Because the envelopes were not initiated in ServiceNow it returns zero results, this causes an error, which in turn logs an issue in the DocuSign Admin console and alerts our DocuSign admins to a configuration problem and results in me getting an email about it 😅
Kind regards,
Ashley
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
a week ago
Yes we actually got successful connection configured.