Skip to main content
Scrive

The «Days must be between 1 and 365.» message in Scrive Connector

The message Days must be between 1 and 365. appears when you press Apply with the mode set to Prolong expiry and a number of days outside that range; the action stops and nothing is saved. To fix it, enter a whole number from 1 to 365 or, if you wanted a reminder, change the mode.

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

What the message means

It is a range check on the Days field, which is a whole-number field. It only applies when the Mode field is set to Prolong expiry: the value must be from 1 to 365, and both ends are accepted. Zero, a negative number or anything above 365 fails. With the default values the check passes: Days starts at 30 and Mode starts at Prolong expiry. The message is in the published code of Odoo 17, 18, 19 and 20.

Code-built diagram, not an Odoo screen: the Apply button, the Days and Mode fields and, below them, the message Days must be between 1 and 365.
Diagram built with code from the module's published code, with the labels in English as in the original text. It applies to Odoo 17, 18, 19 and 20.

Mode offers Prolong expiry and Set auto-reminder, and it is hidden when the screen is opened with a mode already fixed in advance.

Code-built diagram, not an Odoo screen: the same message translated into Spanish, German, French, Italian and Portuguese
Diagram built from the module's published translation files, showing the message in five other languages. With Odoo in English you see Days must be between 1 and 365.
Odoo + Scrive: see who signed, get the sealed PDF
Video: Odoo + Scrive: see who signed, get the sealed PDF

Exactly when it appears

The message appears when you press Apply. The button has no view condition: it is visible in Odoo 17, 18, 19 and 20. This is what the Odoo 20 code does when you press it, in this order:

  • It looks at the mode. If it is Prolong expiry, it checks the days before doing anything else.
  • If the days are not between 1 and 365, it raises the message. The action stops and nothing it was going to change is saved; the document's prolongation is never reached.
  • If the days fit the range, the module carries on with prolonging the document and, if that goes well, leaves a note reading Signing period prolonged by … day(s).. That part has its own checks on the document, which are no longer this message.
  • If the mode is Set auto-reminder, this message does not appear: the code goes through a different check on the days, with its own range and its own notice.

Case: the prolongation Marta cannot apply

Example Illustrative case: the company and its figures are made up to explain the flow.

Mercería Levante, a company invented for this case, has sent a contract for signature through Scrive and the customer asks for more time. Marta, in administration, opens the prolongation screen and leaves Mode on Prolong expiry. In Days she types the number of days in a year and a half, a value above 365, and presses Apply. Days must be between 1 and 365. appears and the action stops without prolonging anything.

Marta then tries zero. Same message: in prolongation mode the range starts at 1. Finally she enters a value inside the range and presses Apply; this time the check passes and the module carries on with the prolongation.

Pablo, her colleague, wanted something else: an automatic reminder. He left Mode on Prolong expiry, typed a value outside 1 to 365 in Days and got the same message, because that mode checks that range. He changed Mode to Set auto-reminder and pressed Apply; in that mode the code no longer applies this range but a different check on the days, with its own notice.

What the case shows: the message is not about dates or reminders, only about the number in Days when the mode is prolongation. Before changing anything, look at what Mode says and which number is in Days.

How to fix it

  1. Look at the Mode field. If you want to extend the signing period, it must be on Prolong expiry. If you cannot see it, the screen has been opened with a mode already fixed in advance.
  2. In Days, enter a whole number from 1 to 365. Both 1 and 365 are accepted.
  3. Press Apply again.
  4. If you wanted a reminder, change Mode to Set auto-reminder and press Apply.
  5. If you need more than 365 days, bear in mind that in prolongation mode the code does not accept more.

What to check afterwards

If the prolongation goes ahead, the module leaves a note on the document reading Signing period prolonged by … day(s)., with the number of days you applied. If the message appears again, the value in Days is still outside the range, or the mode is not the one you thought.

Keep in mind too that the starting value in Days, 30, is inside the range: if the message appears, the number in Days is not that one, or it changed before you pressed Apply.

If you have not sent the document yet, it helps to see how sending works step by step before prolonging anything.

How FlexigoTech can help

Scrive Connector is published on Odoo Apps for versions 17.0, 18.0, 19.0 and 20.0; you can see the Odoo Apps listing and the module page on flexigotech.com. FlexigoTech implements Odoo 17, 18, 19 and 20 and builds custom connectors and integrations, so if your signing workflow needs more, we can look at it with you.

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.Scrive Connector: «Odoo could not produce the PDF», when it appears and how to fix itWhy Scrive Connector says Odoo could not produce the PDF and sends nothing for signature: when it appears, what it means and how to fix it.
Checked in the connector's source code (version 20.0) and the linked sources

Sources