Skip to main content
Scrive

The Scrive Connector error: Only signed documents can be forwarded.

The message Only signed documents can be forwarded. appears when you press Forward in the forwarding window and the document's State is not Signed. To resolve it, check the state under Scrive › Signature Documents: forwarding only goes ahead with the document in Signed. Here is the exact condition in the code and what happens before and after.

FlexigoTech · Editor in charge: Víctor Gómez · Updated 5 November 2026

Key facts

Module
Scrive
Versions
Odoo 17, 18, 19 and 20
Checked
in the connector's source code, version 20.0 · against the sources linked at the end
Reading time
3 min

What the message does not tell you

The module checks the state when you confirm the forwarding

In the forwarding window, the Forward button is always visible (Odoo 17, 18, 19 and 20). It is when you press it that the module checks the document is in Signed. If it is not, the action stops and you see Only signed documents can be forwarded.

The check looks at the State field of the document you want to forward. To find out its value, open the document and look at that field, as described below.

The condition is a comparison with the Signed state

The forwarding code raises the message when the document's State field is not Signed. It is the first thing forwarding does with that document, before talking to Scrive. The Forward button in the forwarding window gets there: its confirm action goes through the forwarding method, which raises the warning if the condition is met.

Diagram made with code: the Scrive › Signature Documents menu, the Forward button, the State field and the message Only signed documents can be forwarded.
Diagram made with code from the module's published code (not an Odoo screen): from the menu to the button and the state field, and from there to the message. It applies to Odoo 17, 18, 19 and 20.

Any other State value triggers it

The check only asks whether the state is Signed or not: anything other than Signed gets in. The values of the State field are Draft, Preparation, Awaiting Start, Pending, Signed, Canceled, Timed Out, Rejected, Error and Saved as Template. With any of them except Signed, forwarding stops with this message.

So a Pending document and a Rejected one get exactly the same warning: the module does not tell them apart, it only checks whether the state is Signed.

The action stops before touching anything

When the state is not Signed, the code cuts off right there: no request is made to Scrive to forward the document and no note is posted on it. Nothing the action was going to change is saved.

Where to look at the state before forwarding

The document records open from the Scrive › Signature Documents menu. The Scrive menu level requires the User permission: if you do not have it, you do not see that level. The State field shows on the Signature Documents form and in its list.

  1. Open Scrive › Signature Documents and find the document.
  2. Look at its State, on the form or in the list.
  3. If it says Signed, forwarding passes the check.
  4. If it says anything else, the module will not forward it until the document is in Signed.
Kanban view of Signature Documents with columns Signed, Draft, Pending, Rejected and Saved as Template, and cards showing a reference, a title and a signature count.
Kanban view of the signature documents with demonstration data (the titles carry the DEMO tag); the last column is cut off.

What happens when the document is Signed

Once the check is passed, the module asks Scrive to forward the document to the email address given when forwarding. It then posts a note on the document itself recording the forwarding to that address, and the action ends.

That is the order in the code: first the state check, then the request to Scrive, and finally the note on the document. With a state other than Signed only the first step runs, which is why, when you see this message, the document never even reaches Scrive.

It is the same message in all four versions

The message is in the published code of branches 17, 18, 19 and 20, and the module is published on Odoo Apps for those same versions. The method code we have described is that of Odoo 20.

If you are starting from the other end of the flow, see what the «Send» button does or another module message that depends on the document's state.

Odoo + Scrive: see who signed, get the sealed PDF
Video: Odoo + Scrive: see who signed, get the sealed PDF

How FlexigoTech can help

FlexigoTech implements Odoo 17, 18, 19 and 20 and builds connectors and bespoke integrations. If you want to look at the module, there is the Scrive Connector page and its listing on Odoo Apps.

Keep reading

What the Send button of Scrive Connector does, step by stepWhat the Send button of Scrive Connector does in Odoo: what it checks, what it creates, where it takes you next and which messages can stop it.Scrive Connector: «Callbacks can only be triggered for sent documents.»When the callbacks error shows up in Scrive Connector for Odoo, which condition triggers it (document state and Scrive ID) and how to fix it.The «Days must be between 1 and 365.» message in Scrive ConnectorWhen Scrive Connector shows «Days must be between 1 and 365.», what the code checks when you press Apply, and how to fix it.
Checked in the connector's source code (version 20.0) and the linked sources

Sources