Skip to main content

Hi All,

I am implementing Maestro Workflow and it throws errors for various reasons, but error descriptions are not developer friendly to fix those errors easily. For e,g mentioned below error 

{  "name": "Execute_eSign_Scope_47ac200c-b553-4ad9-a1bc-d55afa5d28b4",  "startTime": "2025-06-06T19:30:13.7287018Z",  "endTime": "2025-06-06T19:30:15.4834359Z",  "code": "BadRequest",  "status": "Failed",  "apiError": {    "message": "Error creating envelope for the Esign scope",    "internalErrorCode": "ERR_10999",    "internalTraceId": "047e235f919f7c23850e780df4eb6b0b",    "apiError": "{\"errorCode\":\"UNSPECIFIED_ERROR\",\"message\":\"Object reference not set to an instance of an object.\"}" -- This error does not tell me what is missing to pass into workflow for e.g. whether I am missing to pass any recipient details, or mandatory fields info, then what mandatory field is throwing this error. Without knowing exact errors, it is very difficult to fix quickly, it becomes almost impossible and takes many days due to no clarity on errors  }}

 

If there is any other way to check more detailed errors, it would be really make developers life easy

could you share the setting screenshot of your workflow?

 

FreeLink/甫连信息
🌍 DocuSign Partner | Partner Profile
🌟The only DocuSign Partner globally with two Certified eSignature Technical Consultants

🏆 DocuSign 2024 APAC Reseller Growth Partner of the Year
💡 Ranked #1 in the OG All Star category in DocuSign Community Wrapped 2024
📊 DocuSign Community Leaderboard Top 5 contributor
🚀 Expertise in DocuSign integrations with on-premises systems for leading enterprises across various industries
🔗 Connect with me on LinkedInhttps://www.linkedin.com/in/gehengfeng


There is no such things in Maestro or can you guide me where should I find it?


Hi SST,

Thanks so much for your feedback.

You're 100% correct that more descriptive errors would go a long way in helping developers troubleshoot issues in their Maestro workflows. I’m going to share this with our product team so we can look into adding more detailed error messaging in the future.

Please don't hesitate to share any other suggestions or insights with our team!


Reply