Signatures stop working after an update: your field has the same name as a new Simple Signature field

Last updated 27 Oct 2026

The short version

Your org can add its own fields to the ß Signature object. A later Simple Signature version can add a field with the same name. Then the two fields clash, and signatures stop working. Rename your own field, and signatures work again.

What you see

After you update Simple Signature, signatures stop working. Simple Signature keeps trying to connect, or signature requests are made but never go out. The debug log shows an error about a duplicate field name.

Why it happens

A field your org made has the same name as a field in the new version, so the names conflict.

An example: for the initials feature of version 5.7.52, TAF's steps told admins to make their own field with the name Initials__c. Version 5.8 then added its own Initials field. Orgs that had made Initials__c got the clash when they updated. The same can happen with any field name in any release.

Find the field that clashes

1. Open Setup. Click Object Manager. Click ß Signature. Click Fields & Relationships. The list of fields opens.
2. Read the Field Name column. Simple Signature fields start with signature__. Your own fields do not.
3. Look for two rows with the same name, one with signature__ in front and one without. For example, signature__Initials__c belongs to Simple Signature and Initials__c is yours. The two rows can have the same label, so compare the Field Name column. Your field, the one without signature__, is the one that clashes.

If no field matches, this article does not fit your problem. Open a case.

If a PDF template uses your field with a merge code, open a case before you rename. TAF support tells you what to change in the template.

What to do

1. In Fields & Relationships, find the row of your field by its Field Name. Click the link in the Field Label column of that row. The field's page opens.
2. Click Edit. The edit page opens.
3. In Field Label, add (custom) to the end of the text. Now you can tell your field from the Simple Signature one.
4. In Field Name, add _Custom to the end of the text. For example, Initials becomes Initials_Custom. Click Save. The field's page opens again and shows the new API name, for example Initials_Custom__c.
5. Take a test signature, or send a test signature request, the same way your users do.

How to check it worked

1. For a signature on a record: the signature saves, and a new ß Signature record shows it.
2. For a signature request: the signer gets the request email.

If it still does not work

Open a case. Include your Simple Signature version and the old and new names of your field.

Was this helpful?

Yes No

Related

• All Simple Signature troubleshooting
• Install the newest version of Simple Signature. TAF works on bugs in the newest version only.