This topic contains 1 reply, has 2 voices, and was last updated by  Haris 2 months, 3 weeks ago.

  • Author
    Posts
  • Participant
    cpomeroy
    Member since: 02.08.2016
    Number of posts: 19

    Hi,

    We’re investigating a production issue where some packages are not completing, even though they appear to be complete. They return a status of “SIGNING_COMPLETED” when queried via the REST API. We’re not sure why, as the package has autocomplete set to true, and have no attachments that would prevent automatic completion.

    I’ve compared the JSON for packages that have not completed with those that have, and the only real difference seems to be that on successfully completed packages, each document seems to have the following data attribute:
    “documents”: [
    {
    “status”: “”,
    “description”: “Must be accepted and agreed to before starting the signing process.”,
    “id”: “default-consent”,
    “data”: {
    “ese_document_texttag_extract_needed”: “false”
    },

    For packages that aren’t completing (returning a status of “SIGNING_COMPLETED” instead of “COMPLETE”), this looks as follows:
    “documents”: [
    {
    “status”: “”,
    “description”: “Must be accepted and agreed to before starting the signing process.”,
    “id”: “default-consent”,
    “data”: {},

    We are wondering what the “ese_document_texttag_extract_needed” means.

    Also, if you have any suggestions as to what might be preventing autocompletion of some (not all) packages, I’d love to hear about it as well 🙂

    Thanks in advance,
    -Chris

    Keymaster
    Haris
    Guru
    Member since: 05.11.2015
    Number of posts: 969

    Score

    0

    Hi Chris,

    I’m not sure what ese_document_texttag_extract_needed means exactly. I’ll have to ask our maintenance team. It’ll probably go to Monday though since almost everyone is off today due to a holiday (Canada Day). In the mean time, would you be able to share a package id for which all the signatures have been signed but is still in SENT status? I would also advise sending an email to support, as this may be a bug in our application.


    Haris Haidary
    eSignLive Technical Evangelist
    • This reply was modified 2 months, 3 weeks ago by  Haris.

You must be logged in to reply to this topic.