Error Reference
This section documents the errors administrators are most likely to encounter during setup and ongoing operation of Conga Sign 2.0. Errors are organized by the area where they occur. For each error, the likely cause and resolution steps are provided. If you encounter an error not listed here and cannot resolve it with the steps below, contact Conga Support and include the error message text, the area where it occurred, and any recent changes made to your configuration.
Platform Setup Errors
User cannot see the Document Management Application after login
Likely cause: The user's role does not include access to the Document Management Application, or the Conga Sign Permissions group is not assigned.
For Conga Sign Integration User and Admin roles: these should provide access automatically. Verify the role is correctly assigned in .
For auto-provisioned users: the AuthAutoProvisionedUser role does not include Sign access by default. Follow the steps in Roles and Permissions to update the role with the Conga Sign Permissions group and View Document Management Application permission.
If the role appears correct but access is still missing, navigate to and verify the Conga Sign Permissions group is present on the user's account.
User can see the Platform but cannot send transactions
Likely cause: The user exists as a Platform user but has not been added as a Sign sender.
Resolution: Navigate to and use Invite New Sender to add the user. See Conga Sign Settings for full details.
Auto-provisioned user created with wrong role
Likely cause: The AuthAutoProvisionedUser role was not updated before the user logged in for the first time.
Resolution: Update the role as described in Roles and Permissions. The change applies immediately - the user does not need to be recreated. They may need to log out and back in for the updated permissions to take effect.
Salesforce Connector Errors
Data Sync Connection shows red / disconnected status
Likely causes:
The connection was established under a personal admin account rather than the dedicated connector user, and that session has since expired or been disrupted by Salesforce's Refresh Token Rotation (RTR) enforcement.
The dedicated connector user's Salesforce session was explicitly logged out.
The Salesforce org was refreshed (sandbox) and the IDP record is now stale.
Resolution:
Navigate to .
Click Disconnect to clear the existing connection.
Open an incognito browser window and log in to the Platform as the dedicated connector user.
Reconnect from the Data Sync Connections tab.
- If using a sandbox that has been refreshed, first update the IDP record in before reconnecting. See Setting Up a Salesforce IDP Record.Note: Always reconnect as the dedicated connector user, not a personal admin account. A personal account's session will eventually be disrupted again.
Final signed document not syncing back to Salesforce
Likely cause: The Salesforce org has been disconnected from the Conga Platform. The document sync depends on an active Data Sync Connection - if the connection breaks, completed transactions stop writing back.
Resolution:
Reconnect the Data Sync Connection following the steps above.
Once reconnected, navigate to the relevant transaction record in Sign.
- Click the Sync button on the transaction record to manually trigger a retry of the writeback for that transaction.Note: Future transactions will sync automatically once the connection is re-established. Only transactions completed during the disconnected period need to be manually resynced.
Salesforce button fails to launch / no transaction created
Likely causes:
The idp parameter value does not match the environment type (Salesforce vs. SalesforceSandbox).
The idporgid value is incorrect or missing.
The templateid parameter is not placed last in the URL string.
The recipient ID in the button URL is 15 characters instead of 18 - use CASESAFEID() to ensure the correct length.
Resolution: Review the button URL against the parameter reference in Section 4.7. Confirm the idp value matches your environment and the idporgid matches your Salesforce Organization ID. If the issue persists, contact Conga Support with the full button URL (sensitive IDs redacted).
Writeback field not syncing to Salesforce after transaction completion
The Max Length on the text field is not set to 255, and the signer entered more than 255 characters.
The writeback tag in the Field Name references a different Salesforce object than the one the button was launched from.
Periods in the Salesforce field API name were not replaced with _DOT_ in the tag syntax.
The Data Sync Connection was disconnected at the time the transaction completed.
Template Errors
Template not visible to senders
Likely cause: The Share template toggle is not enabled on the template.
Resolution: Open the template, go to Template Details, and enable the Share template toggle. The template will immediately become available to all Sign senders in the account.
Signing fields assigned to the wrong recipient
Likely cause: The wrong recipient was selected in the left panel when the field was placed in the document editor.
Resolution: Click the misassigned field on the canvas to open its Settings panel. Change the Recipient dropdown to the correct signer. Verify all fields before saving the template.
Enforce Document Accessibility setting needs to change
Likely cause: This setting was not configured correctly when the template was first created and cannot be changed after creation.
Resolution: Clone the template, then set Enforce Document Accessibility correctly in the Create New Template dialog before saving the clone. Delete or retire the original template.
Transaction Errors
Transaction stuck / not progressing
If a transaction appears stuck - sent but not moving to the next signing step - verify:
The signing order is configured as intended. If sequential signing is set, confirm the previous recipient has completed their step.
The recipient received their invitation email. Check whether reminder settings are configured.
The transaction has not expired. Check the expiration date on the transaction record.
For persistent stuck transactions, contact Conga Support with the transaction ID.
Recipient did not receive signing invitation
Likely causes:
The recipient's email address is incorrect.
The invitation email was caught by a spam filter.
Email reminders are not enabled and the initial invitation was missed.
Resolution: Verify the recipient email address on the transaction. Ask the recipient to check their spam folder. If needed, resend the invitation from the transaction record in Sign.
Frequently Asked Questions
Why can't my users see Conga Sign after logging in?
The most common reason is that the user's role does not include the permissions needed to access the Document Management Application or interact with Sign transaction data.
Check the following in order:
Is the user assigned the right Platform role? The recommended roles for Sign users are Conga Sign Integration User (for senders) and Admin (for administrators). The AuthAutoProvisionedUser role that Salesforce IDP users receive by default does not include Sign access - it must be updated. See Initial Platform Setup > Roles and Permissions.
Has the user been added as a Sign sender? A Platform user and a Sign sender are not the same thing. Even with the right role, a user needs to be added in Sign Settings → User Management before they can send transactions. See Initial Platform Setup > Conga Sign Settings.
Is the Conga Sign Permissions group assigned? For users on roles other than Admin or Conga Sign Integration User, this group must be manually assigned. It grants the object-level permissions Sign needs to create and update transaction data on the Platform.
Where can my users see transaction status in Salesforce?
Transaction status and details are not automatically synced into Salesforce fields in the current version of Sign 2.0. To view transaction status from within Salesforce, you need to build a View Transactions button on your Salesforce object. This button opens the Sign transaction view directly, showing the current status, recipient progress, and document details.
The Conga Sign Permissions group grants access to the Sign data objects on the Conga Advantage Platform - things like transaction records, package metadata, recipient data, event logs, and connector writeback objects. These permissions are what allow the day-to-day automation of Sign to work correctly: creating transactions, updating their status as signers complete steps, logging events, and writing data back to Salesforce.
Without these permissions, users may be able to log in but will hit errors when Sign tries to read or write transaction data on their behalf - even if the transaction was initiated through a Salesforce button rather than manually.
The Admin and Conga Sign Integration User roles include all necessary permissions automatically. Users on other roles need the Conga Sign Permissions group assigned explicitly. See Initial Platform Setup > Roles and Permissions for the full permissions list.
Why isn't the final signed document syncing back to Salesforce?
The most likely cause is that the Salesforce connection has been disconnected from the Conga Platform. The document sync - including delivery of the signed PDF back to Salesforce - depends on an active Data Sync Connection. When that connection breaks, completed transactions stop writing back.
To resolve:
Navigate to and check the connection status.
If the status is red or disconnected, reconnect following the steps in Salesforce Connector Setup > Establishing the Data Sync Connection. Always reconnect as the dedicated connector user, not a personal admin account.
Once reconnected, go to the affected transaction record in Sign and click the Sync button to manually retry the writeback for that specific transaction.
Transactions that completed while the connection was active will have already synced. Only those completed during the disconnected window need manual resyncing.
See Error Reference > Salesforce Connector Errors for additional connector troubleshooting steps.
How do I set up reminders for signers?
Reminders can be configured at three levels, each overriding the one above:
Account level (applies to all transactions by default): . See Initial Platform Setup > Conga Sign Settings.
Template level (overrides account default for transactions from that template): In the template editor, open Settings and click Configure next to Reminders. See Template Configuration > Stage 1: Settings Panel.
Transaction level (overrides both): Use the reminderDays, repeatReminderDays, and totalReminders parameters in the Salesforce button URL. See Salesforce Connector Setup > Building Salesforce buttons.
If reminders aren't sending, verify that they're enabled at least at the account level, and that the Send Email Reminders toggle is on in Email Reminder Settings.
How do I control when a transaction expires?
Like reminders, expiration can be configured at three levels:
Account level: Sign Settings → Sent Transaction Expiry Time. Sets the default number of days and the maximum extension a sender can apply. See Initial Platform Setup > Conga Sign Settings.
Template level: In the template Settings panel, configure Expiration as Day(s), a fixed Date, or Unlimited. See Template Configuration > Stage 1: Settings Panel.
Transaction level: Use the expireDays or expireOn parameters in the Salesforce button URL. See Salesforce Connector Setup > Building Salesforce Buttons.
Note that expireDays and expireOn cannot be used together - choose one. If neither is set on the button, the template or account default applies.
Can I use the same template for multiple Salesforce objects?
Yes, with one important caveat for writeback: writeback only works for fields from the Salesforce object the button was launched from. If your template uses writeback tags for Opportunity fields and a sender launches it from a Contact record, the writeback will fail for those fields.
For templates used across multiple objects, either omit writeback tags or create object-specific versions of the template with the correct writeback tags for each object.
What's the difference between Data Retention and Sent Transaction Expiry Time?
These are two separate and commonly confused settings:
Sent Transaction Expiry Time controls how long a transaction stays open for signing before it automatically closes. This is a deadline for the signing process itself.
Data Retention controls how long transaction records and documents are stored on the Platform after the transaction reaches a given status. This is about storage and deletion of completed (or otherwise closed) transactions.
A transaction can expire (stop accepting signatures) and still be retained in the system for months or years, depending on your Data Retention settings. Conversely, a completed transaction with a short Data Retention setting will be permanently deleted after the retention period even if all parties signed successfully.
See Initial Platform Setup > Conga Sign Settings for full details on both settings.