Skip to main content
Scrive

Scrive Connector: «the signing stage must be 1 or higher», and how to fix it

The message Party '…': the signing stage must be 1 or higher (got …). appears when you save a party whose Signing Stage field is below 1; set it to 1 or more and save again.

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
4 min

When this message appears, according to the code

Scrive Connector checks the signing stage of each party at the moment you save. If the value is below 1, the record is not saved and Odoo shows the message. It is an error that stops the action: nothing you were about to change is saved.

There is a single condition: the stage is lower than 1. Because the field is a whole number, zero or any negative number triggers it; 1 and higher numbers pass. The module carries this check in the published code for Odoo 17, 18, 19 and 20.

The Signing Stage field is shown in the Parties tab, inside the Parties table. Its default value in the code is 1.

Diagram built from code (not an Odoo screen) showing the flow: saving with the Signing Stage field and, below it, the error message; labels are in English, as in the module code
Diagram of the flow: on saving, the signing stage field is checked and, if it is below 1, the message appears. It is a diagram generated from the published code, with English labels.
Odoo + Scrive: see who signed, get the sealed PDF
Video: Odoo + Scrive: see who signed, get the sealed PDF

How to read the message

The message has three parts, and each one gives you a clue:

  • Party '…': the name of the party that breaks the rule. If that party has no name, you will see Unnamed party instead.
  • the signing stage must be 1 or higher: the rule that was broken.
  • (got …): the value the Signing Stage field had when you tried to save.
Diagram built from code (not an Odoo screen) with the same message in Spanish, German, French, Italian and Portuguese
The message as shown by the module's published translations, depending on the language of Odoo. It is a diagram generated from the translation files.

The comment in the code itself explains where the check comes from: a stage of 0 used to be quietly turned into 1 when the signing data was built, and a negative stage was sent to Scrive as it was.

What happens with each value on saving

Value of Signing StageWhat happens on saving
ZeroThe record is not saved and the message says got 0.
A negative numberThe record is not saved and the message shows that number after got.
1 or a higher numberIt passes this check.

How to fix it, step by step

  1. Read the whole message. The name between the quotes tells you which party is failing (or Unnamed party if it has no name), and the number after got tells you what value was there.
  2. Go to the Parties tab and find, in the Parties table, the party the message names and its Signing Stage field.
  3. Replace the value with 1 or a higher number. Which number to use depends on the signing order you want; the field's help text is quoted below.
  4. Check the other parties in the table. The check goes through the parties and stops at the first one that fails, so if several have a value below 1, the message names one and the others may show up afterwards.
  5. Save again. If the message comes back, look at the value after got … and correct it on the party that is named.

Which number to put on each party

The help text of the Signing Stage field reads: «Parties are invited in ascending stage order; stage 2 is invited once every stage-1 party has signed.»

Two ideas follow from it:

  • Stage 1 is the field's default value and the minimum the module accepts.
  • If a party has to wait for the stage-1 parties to sign, give it stage 2: according to the help text, it is invited once every stage-1 party has signed.

If all you want is to get past the error and you have no order in mind, leave the default value, 1.

What to check after saving

  • That the record saves without the message appearing.
  • That in the Parties table every party has a Signing Stage of 1 or higher.
  • That the order of the stages matches the order in which you want each party to be invited, according to the field's help text.

If you also want to review how a document is sent for signing, there is an article on what the «Send» button of Scrive Connector does.

Cost, and help with Scrive Connector

Scrive Connector is a one-off purchase per Odoo version (published for 17, 18, 19 and 20) and needs a FlexigoTech Cloud subscription, Connector plan: €49 per month or €490 per year, excluding VAT. The connection goes through FlexigoTech Cloud, which stores the credentials encrypted, monitors synchronisation and emails you if it fails. You can see the listing on Odoo Apps or the module page on flexigotech.com.

FlexigoTech implements Odoo 17, 18, 19 and 20 and builds custom connectors and integrations.

Last updated: November 2026.

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