Document uploaded using private API token never leaves "Processing" state

  • 1
  • Problem
  • Updated 6 months ago
We are uploading documents using a private API token.  We manage to upload without any errors, as far as we can tell.  However, the document never leaves to "Processing" state and finishes up at RightSignature.

RightSignature never sends out the emails or shows the document on the account on-line.  When I query the sending_request using the GUID , I get back a new document id, and status of "processing" and a status message of "File successfully downloaded".  

If I query the status on the document ID, the recipients have been dropped, and the status of the document is "draft".  Has something changed in what should be sent when setting up the document? Why would my recipients disappear?
Photo of Caryn Babstock

Caryn Babstock

  • 5 Posts
  • 0 Reply Likes

Posted 6 months ago

  • 1
Photo of Saravanan Kannan

Saravanan Kannan, Employee

  • 36 Posts
  • 6 Reply Likes
Caryn,

I looked at one of your sending request dated 18 Apr 2018. I am seeing an error 'Invalid MIME type (application/zip)' for one of your doc file while processing the base file you uploaded in our logs. Could you be able to try with a simple pdf/doc file to see if it has something to do with the file you are uploading? I assume you are making PUT request to the upload url with your pdf/doc file. Also pls let us know how you are making that request?

Thanks
Saravanan
Photo of Caryn Babstock

Caryn Babstock

  • 5 Posts
  • 0 Reply Likes
I'm not setting explicit headers at all for the put request  of the file, not even the Authentication string.  What should the content type be?  The file is a doc file - it's not zipped in any way, but it appears that the browser is interpreting it as zipped for some reason.

Should I be setting the Content Type to "Application/msword" for doc or docx files?  Will that solve the issue?

Is there anyway to retrieve these kinds of errors myself?  I can't see anything in any of the response to queries, on either the document or on the sending_request. 
Photo of Saravanan Kannan

Saravanan Kannan, Employee

  • 36 Posts
  • 6 Reply Likes
Caryn,

Content type - 'application/pdf' should work.

Thanks
Saravanan