Salesforce Userlicense Object
Giovanni Sealy
If the above steps do not resolve your issues, please browse our common errors and resolutions guide below. Pro Tip: To save time, use your browser's search function to search for keywords from your error.
Salesforce requires Multi-Factor Authentication (MFA) for all users. This means "High Assurance" setting in Session Setting is enabled by default. However, "High Assurance" being enabled restricts the asynchronous processing performed by S-Docs Jobs and causing them to fail or produce corrupted files.
To resolve navigate to the Setup menu > type "Profiles" into the QuickFind bar > click Profiles in the dropdown menu > Then, click Edit next to the appropriate profile name. > Find the Session Settings section, and ensure the Session Security Level Required at Login is set to None (not High Assurance).
This error is typically tied to the function that is being used in the template. It likely to occur when merge fields within this MATH function resolve to NULL or when the amount of digits after a decimal in the merge field do not align with the number of decimals spaces that the format-number attribute allows.
-This error is most commonly encountered when two SDoc Jobs concurrently attempt to process the same record. To address this, we recommend inserting a delay between the creation and execution of the SDoc Job.
-If you have recently upgraded to or on S-Doc version 4.516.30 and are experiencing this issue, we advise updating to a more recent package (versions 4.516.35+). This error has been identified as a known bug in version 4.516.30 and has been fixed in subsequent releases.
This error implies that the overall file size of the generated document is too large. Often times an easy way to adjust for this is to look for any images and upload versions of those images that are smaller in file size. Another way to work around this is to take advantage of component templates to split your template.
This error occurs when the template(s) have syntax errors, commonly as a result of pasting source code into the WYSIWYG editor. Check the template source to ensure that the proper tags are used correctly (i.e. "
Duplicate rules are often setup to prevent duplicate contacts from being created. Typically, these are set up for contact records. Since the No Contact Record is being inserted, and subsequently deleted, many times you may run in to this error if the record is being added multiple times before deletion.
You can try using option 1 as outlined in the following documentation for the no contact record without updating the S-Docs button. Alternatively, you can provide field-level security access to the user profile generating the document for the field.
Mass Merge can occasionally get stuck at "pending file creation" when using HTML templates that have "create salesforce file and link to record" checked. This can be fixed by instead unchecking this and creating an attachment.
If the error is being displayed while using Mass Merge this could be due to the SDocsSettings being misconfigured or missing. Check your SDocsSettings and Mass Merge setup and make sure that everything is configured correctly.
This is a known issue that occurs when selecting several records after clicking on the Mass Merge button in the list view.
There are 2 ways to avoid this:
1. Select the records prior to clicking on the Mass Merge button.
2. Another alternative is using Mass Merge in batches of 50, up to 100 records. Batches of 50 are most successful.
This error can occur if you are attempting to send an e-signature request with a PDF that is not S-Sign enabled. This commonly happens when users select a correct S-Sign-enabled email template but not a correct S-Sign-enabled PDF.
1. Go to remote site settings and ensure that there are remote sites for the org (This will be the domain for the org which can be found in the url in classic or by clicking on the profile icon in the top right). This sight should also be marked as active.
3. Check the SDocs Connected apps setting to make sure that "Access Connect REST API resources (chatter_api)", "Manage user data via APIs (api)", and "Perform requests at any time (refresh_token, offline_access)" OAuth scopes are set.
ConnectedAppUserName: If you are configuring S-Sign e-signatures, enter a username to be used as the S-Sign Internal User (we recommend using an administrator's user name). The S-Sign Internal User will be the user which all S-Sign operations will be conducted by through the secure S-Docs Connected App.
If this is occurring during the S-Sign Process then the templates may need to be checked to ensure they are S-Sign enabled as well as making sure that the S-Sign envelope lookup field is configured correctly. It is also good practice to check through all of your configuration steps and insure there is nothing missing or misconfigured from the guide.
Conditional logic in templates can also cause this error when used on many different records. If the conditional logic is complex with multiple levels, it can sometimes lead to attempting to search for a field value that doesn't exist causing this error.
In previous versions, S-Sign notification reminders were handled in a way that queried for every notification individually and led to this error. This process has been since updated and improved S-Sign 2.299.22+ Please update your S-Sign package to the latest version.
This typically occurs when the S-Sign input tag(s) are malformed. Please ensure that all S-Sign input tags are in the following syntax:
[[SSIGN_INPUT ID=X]]
Note: The tag must be complete and should not be broken up with styling placed within the tag.
This will happen if the ConnectedAppTokenURL in the SDocs Custom Settings is incorrect. Please review our knowledgebase article for S-Sign configuration and make sure that the correct URL is put in the ConnectedAppTokenURL field.
Before attempting to troubleshoot S-Doc Job errors, we recommend navigating to the template record(s) being used with the S-Doc Job and running a Save & Preview. If the document does not generate successfully, your issue likely has to do with the document template itself. If the document does generate successfully, move on to the troubleshooting information below.
Note: When auto-creating S-Docs through S-Doc Jobs, the Status field on the S-Doc Job record will indicate whether a Job has completed successfully or an error occurred. The following will give an explanation of what each Status field state means.
When using job splitters in a template, you may come across this SDCreate3 Initialization Error. This can be caused by several different issues including an out of date version of S-docs or proper permissions that need to be given. When the job splitters are removed from the template in question, the true underlying issue/errors should surface. Removing the job splitters and running the template again should give you a more useful and descriptive error.
Please check the following:
-Ensure that the user running the job has a S-Docs permission set applied.
-If the SDoc Template object being set to Private then you may need to create a Sharing Rule to override it.
-If the user has a permission set group, ensure that the permission set group does not restrict access to the SDoc Template object.
"Too many queueable jobs added to the queue:2" occurs when an error occurs but we fail to catch it and update the S-Docs Job status to 'Error'. If you check the logs in Setup > Apex Jobs, you should see an error message.
Founded in 2010, the S-Docs team is led by a former Director and Technical Architect from Salesforce and is comprised of experts in Salesforce and document solutions. S-Docs is now used by thousands of global subscribers from all industries with a multitude of use cases, but they all share one key theme: The need for a powerful yet easy-to-use native solution. We are proud that they have made us the #1 native document generator and e-signature solution and put us in the top 1% of all apps on the Salesforce AppExchange.
2024 S-Docs Inc. All Rights Reserved Privacy