Attempting to use sample Adobe Sign Spoke Flow Action "Upload Attachment as Transient Document" results in 404 responseIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } When viewing Flow Execution details for the failing action, an error is displayed: Error: ,Detail: Unexpected token: < As a result the user is unable to upload a so-called "transient document" to the Adobe Sign API endpoint for further processing. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } All Releases compatible with Adobe Sign Spoke plugin Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } When looking deeper at the Flow Execution details, you should see a similar error as follows: Method failed: (/public/oauth/v2/token/api/rest/v6/transientDocuments) with code: 404 Check outbound HTTP log and/or Splunk for entries correlating to the above 404 failed error. e.g. 2025-07-25 10:16:54 (558) worker.6 worker.6 txid=a4bd274c1bcb SHA_f89e023153a03300e8cbddeeff7b12ab OUTBOUND_НТТР: protocol=HTTP/1.1 response_status=404 response_time=521 request_length=38342 response_length=25156 app_scope=sn_adobesign_spoke session_id =glide.scheduler.worker.6 transaction_name="Flow Engine Event Handler - system" transaction_id=a4bd274c1bcbae102beec958624bc69 8 user_name=system mid_server= source_table=sys_hub_step_instance source_record=UNKNOWN system_id=app-redacted.redacted. service-no w.com:redacted002 method=POST log_level=Basic scheme=https hostname=secure.na4.adobesign.com path=/public/oauth/v2/token/api/rest/v6/transientDocuments Note the "path" value above. Per Adobe, they have two different API endpoints for token generation/management and for actual doc signing transactions. The 404 error clearly mashes or concatenates the token API and transientDocument API endpoints. There is no such URL available from the Adobe infrastructure and thus you get a 404 response. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } When the flow action executes, it takes the Connection Details data specified in the flow's Step 2->Upload Attachment As Transient Document and concatenates it with the Resource path value in the Request details section; e.g. To correct the issue review the Connection Alias being used by the Flow -- you will see the actual record's name in the Flow Execution details that you must inspect. You should see that the Connection record's URL is incorrectly specified; e.g. https://secure.na4.adobesign.com/public/oauth/v2/token There is no need to specify anything after the fully qualified domain name. Simply remove the "/public/oauth/v2/token" portion. Related Links<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } https://www.servicenow.com/docs/bundle/xanadu-integrate-applications/page/administer/integrationhub-store-spokes/task/setup-adobe-sign.html#title_register-adobe-sign-oauth