Skip to main content
Schenley217874661a64
Schenley217874661a64
Participant
June 18, 2018
Answered

Error: The Agreement ID specified is invalid

  • June 18, 2018
  • 3 replies
  • 10918 views

I am assisting a unit we support to set up a workflow for one of their processes. 

  • We've created a SharePoint site to store unsigned contracts and request details. 
  • The three staff members have Adobe Sign accounts and are able select files in SharePoint to "Send for Signature."
  • One is a Group Admin in Adobe Sign and all three are in the group.

 

We want the signed files to be saved to this SharePoint site.  The Flow I set up with the Group Admin initially worked - it uses the "When an agreement workflow is completed successfully" trigger, with the scope "Any agreement in my group."

 

When the other two users tried sending a file for signature the Flow triggered and the initial steps ran, but it failed at the "Get a PDF of a signed agreement" step, with this error:

 

  "code": "INVALID_AGREEMENT_ID",

  "message": "The Agreement ID specified is invalid"

 

 

I saw in another forum post that someone discovered a different Adobe Sign action fails when the Flow step credentials don't match the user who sent the agreement for signature. 

 

Is that what is happening here? 

 

Is there a way around this, other than duplicating the Flow for each user and having it only trigger for agreements they sent? This is not ideal for maintaining their solution. 

This topic has been closed for replies.
Correct answer SimonATS

In the action Get a PDF from a Signed document, show the advacned options to expose the 'in the name' of field. Populate this with the constant

email:

followed by the sender dynamic value of the trigger:

 

 

Note this does assume that the Sign user who has created the connector is a group or account admin and has therefore got the permissions over the sender.

 

As an aside, you're using 2 integrations, the sharepoint integration to create the agreement and the PowerAutomate to process it. You can also handle the creation of the sign agreement (in a new flow) by sing the Sharepoint trigger

'from a selected item' or 'from a selected file'.

 

This added the name of the flow under the Automate context menu in Sharepoint. 

It gives you a bit more control on how agreements are created if needed.

3 replies

S
Sai Krishna N
Participant
March 3, 2022

Hello,

 

We are noticing our integration with Adobe Sign failing with error message "INVALID_DOCUMENT_ID" in the Azure Logic App, which enables the integration to Adobe Sign to fetch the Agreement and its related documents. We are noticing an issue with the Adobe Sign integration erroring out sometimes which is breaking our logic app in performing the subsequent actions defined in it. This is an intermittent issue which occurs only sometimes and when we retrigger our integration it executes without erroring out. 

 

Input Request: /v6/agreements/{agreementid}/documents/{documentid}

Output:

{

    "statusCode": 404,

    "headers": {

        "Pragma": "no-cache",

        "X-Robots-Tag": "none",

        "x-request-id": "XXXXXX-XXXXXXX",

        "Strict-Transport-Security": "max-age=31536000;",

        "X-XSS-Protection": "1; mode=block",

        "X-Content-Type-Options": "nosniff",

        "Timing-Allow-Origin": "*",

        "x-ms-apihub-cached-response": "false",

        "x-ms-apihub-obo": "true",

        "Cache-Control": "no-store, must-revalidate, no-cache",

        "Date": "Wed, 23 Feb 2022 15:20:08 GMT",

        "P3P": "CP=\"IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT\"",

        "Content-Length": "91",

        "Content-Type": "application/json",

        "Expires": "0"

    },

    "body": {

        "code": "INVALID_DOCUMENT_ID",

        "message": "The Document ID specified is invalid"

    }

}

S
Community Manager
SimonATSCommunity ManagerCorrect answer
Community Manager
November 17, 2021

In the action Get a PDF from a Signed document, show the advacned options to expose the 'in the name' of field. Populate this with the constant

email:

followed by the sender dynamic value of the trigger:

 

 

Note this does assume that the Sign user who has created the connector is a group or account admin and has therefore got the permissions over the sender.

 

As an aside, you're using 2 integrations, the sharepoint integration to create the agreement and the PowerAutomate to process it. You can also handle the creation of the sign agreement (in a new flow) by sing the Sharepoint trigger

'from a selected item' or 'from a selected file'.

 

This added the name of the flow under the Automate context menu in Sharepoint. 

It gives you a bit more control on how agreements are created if needed.

Schenley217874661a64
Schenley217874661a64Author
Participant
November 17, 2021

THANK YOU so much!  This is an important project for us, as they are piloting the adoption of Adobe Sign in our organization.  It's exciting to have this first workflow set up for them to go live with after the holidays. 

    R
    ROGELIO JONAT257091754l24
    Participant
    August 25, 2022

    Hello SCHENLEY, could you share the flow with us, please?

    K
    Koram
    Participant
    June 18, 2018

    I can't sign a contract because I have this signal: The Agreement ID specified is invalid. What does it mean? How can I sign the contract?

      sameer_puri
      Adobe Employee
      sameer_puri
      Adobe Employee
      June 18, 2018

      Hi Koram,

      Can you please inbox (AND NOT POST HERE) me the signing URL so that I can take a look?

      Thanks

      Sameer Puri

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices