The messages senders and recipients see most often, what they mean, and what to do. Messages are shown as they start; the rest of the text gives the details.
When you send or preview an agreement
These appear in the Create JuicedSign Agreement or Preview Agreement window. Most start with Unable to create an agreement - or Error occured while getting agreement details.
Setup and parameters
Message | What it means and what to do |
|---|---|
Missing the required parameters… | The button is missing a required parameter. Compare it with Button parameters, or run the wizard again. |
JuicedSign sending email address is not setup… | JuicedSign Sender Email isn't an active sender in your account, or you have no default sender. Add or activate the sender on the Users tab. See Account settings and senders. |
The expiration days value cannot be zero… | Expire After is 0 or empty, and so is your account default. Set Expire After on your record, or the default in Account Settings. |
Please check the draw and font signature specifications in your formula query |
|
The signed document info parameter (signeddocinfo or signeddocfafid) is missing… | The button doesn't say where to save the signed document. Add |
Signed doc info parameter is not properly formatted…, Invalid cloud type passed in the signed document info parameter. | Fix Signed Document Info. See Where to save. |
The document
Message | What it means and what to do |
|---|---|
Unable to get the document from the file attachment field…, …from the repository table's file attachment field…, …from S3…, …from Dropbox… | The record has no document where Agreement Doc Fids points. Attach the document, or fix the S3 key or Dropbox file name. |
Docfids parameter is not in the correct format…, Docfids field is not in the correct format…, Invalid cloud type provided in docfids parameter… | Fix Agreement Doc Fids. Only one document per agreement. See The document. |
The document … is more than 20MB in size… | Make the document smaller than 20 MB. |
Please upload file in the pdf/docx format., You cannot include documents of the type… | Use a PDF or Word (.docx) file. |
The file name … contains an invalid character…, File name is not valid… | Rename the file without |
Recipients
Message | What it means and what to do |
|---|---|
Recipient string is not in correct format!, Missing Recipient information… | An entry in Recipient String doesn't have all seven parts, or a name or email is empty. See Recipients. |
Recipient email address … is not valid… | The address failed the email check. Correct it, or use another one. See Email address checks. |
Recipient with email address … has previously chosen to unsubscribe… | Use another address, or have the recipient resubscribe. See Resubscribe. |
JuicedSign does not support parallel signing… | Two signers have the same signing order. Give each signer its own order. |
Captive recipient is not configured correctly… | Only the first signer can sign in person. See In-person signer. |
You have included recipient … as captive recipient. You cannot create an agreement with a Captive recipient with JuicedSign Batch Application. | Batch agreements can't have an in-person signer. Set Captive Recipient to |
Tags
Message | What it means and what to do |
|---|---|
Unable to find tags for this recipient… | A signer has no tags in the template. Add tags with their Recipient ID. |
You must have at least one required signature, initials or approval tag for a recipient. | Give each signer a Signature, Initials, or Approve or Decline tag that isn't Ignore if Not Present. |
Anchor string not found… | A tag's anchor text isn't in the document. Fix it, or check Ignore if Not Present. See Place tags with anchor text. |
You can only have one Approve or Decline tag for a recipient, You cannot have Approve or Decline tag together with signature tags…, You can only include either Signature tag(s) or Signature (Name Editable) tag(s)…, One tag cannot be both optional and required…, …checkbox tag(s) where the font size is greater than the height…, …invalid values for page number… | A tag rule isn't met. See Rules JuicedSign checks when you send. |
JuicedSign shows only one message at a time. After you fix it, send again to see whether there's another.
When you void, resend, or reset
Message | What it means and what to do |
|---|---|
Please enter the reason to void the agreement. | A reason is required to void. |
You cannot void an agreement that is already … | The agreement is already completed, declined, or voided. |
This recipient … is not in the signing order that is being processed currently… | You can resend only to the recipient whose turn it is. |
…it does not match with the status that we have in our records… | The record changed since you opened it. Refresh the record and try again. |
See Manage agreements.
When a recipient opens or signs
Most of these appear on a WHOOPS! page, with an error code and a message.
Message | What it means and what to do |
|---|---|
Hi! You are seeing this screen because: Either, you have entered a incorrect Access token… Or… you may have reached the limit for that access token… (ACCESS_URL_WRONG_OR_MAX_HITS_REACHED) | The access token is wrong, or the link was opened more than the allowed number of times. The recipient should use the newest JuicedSign email, or ask you to resend. See When a signing link stops working. |
The agreement you are attempting to sign has been voided. (ALREADY_VOIDED, ALREADY_DECLINED_TO_SIGN) | The agreement was voided or declined. Send a new agreement if needed. |
The agreement you are attempting to sign has been completed. (ALREADY_COMPLETED) | Everyone finished, or this recipient already signed. Nothing to do; the signed copy comes by email. |
The agreement you are attempting to sign has expired. (ALREADY_EXPIRED) | Send a new agreement. |
The agreement you are attempting to sign has a wrong status information… (STATUS_MISTMATCH) | It isn't the recipient's turn, or a status was changed by hand. Check the agreement's and recipient's statuses. |
Note! The code that you entered is invalid… | Wrong access code. The page shows how many tries are left. The code is case-sensitive. |
Maximum number of tries exceeded | Five wrong access codes. Reset the counter. See Access codes. |
There was an error while loading data into some of the fields of your document… (QB_DEFAULT_FID_DATA_FETCH) | A tag's default value couldn't be read from your record. You also get a default tag value error details email. Fix the tag's QBDefaultfid and resend. |
Uh Oh! looks like we have a problem. Please close your browser completely… (TERMINATED) | The recipient reused a finished session. Close the browser and open the email link again. |
Please Access the Agreement by clicking on the link in your email | The page was opened without the email link, for example by copying the address. Use the link in the email. |
Uh Oh! Something Went Wrong. | An unexpected problem, for example the page was left open for more than about 20 minutes. Open the email link again and start over. If it keeps happening, contact the sender. |
Problems you hear about by email
What to do | |
|---|---|
…default tag value error details | Fix the QBDefaultfid of that recipient's tags, then resend. |
…Quickbase update field error details | The recipient finished, but their entries weren't saved to your table. Fix the QBUpdatefid fields: the target field must exist and accept the value. |
Reset JuicedSign Security Access Code for : … | A recipient used up their access code tries. Reset the counter. |
See Emails to the sender.
When the signed files can't be saved
Unable to upload signed documents to S3 -, …to Quickbase -, …to Dropbox -: the agreement was completed, but the signed files couldn't be saved where Signed Document Info points. The message is in JuicedSign Error Details on the JuicedSign Management record.
Check the field IDs in Signed Document Info and your storage. See The signed document.
Batch
For batch agreements, the message is written to JuicedSign Error Details on the record. The messages are the same as above.
The following parameters do not match the configuration…: a batch argument doesn't match its batch configuration. See Batch Config Portal messages and troubleshooting.
Some problems don't show in the field, such as a sender that isn't set up. If no agreement is created and the field is empty, send the same record with Send to JuicedSign to see the message. See If no agreement is created.