Maintenance

The Tygron Platform undergoes continuous development and improvements, to improve and expand the user experience. To make this possible, moments of maintenance are instituted during which service may be limited, with some instances being more impactful than others.

Tygron aspires to always be as clear as possible with the timing and impact of these periods. There are a number of classifications of maintenance.

Large maintenance window

• When: Approximately once every two years, on friday evening after office hours (GMT+1) with a possible extension into the weekend.
• Duration: Approximately a day,
• Impact: Pausing of services

Large maintenance takes place as a process of releasing new features. These may include significant changes in how data is internally structured and stored, or new, changed, or expanded functionalities. While the release of new versions of the software is of itself rather quick, the majority of time is taken up by automatically updating Project data to function correctly with the new version of the Tygron Platform. These moments are communicated ahead of time via the client application, and via pro-active newsletters starting 2 months ahead of the release.

During this period the server is temporarily taken offline to process the update, resulting in a pause of services. Any actively running sessions will be temporarily unreachable and any calculations will be suspended.

When maintenance is completed and the server is brought back online, all paused and suspended activities will be resumed. Sessions will be restarted, maintaining the state they were in before the maintenance (including any unsaved work). Calculations will resume from the point where they were suspended. However, note that the nature of a release may impact calculation details.

Despite process and infrastructure being intended to resume all activities as if no interuption has taken place, and larger releases to be backwards-compatible with previously set up calculations, it is recommended not to have unsaved work or long-running calculations with this maintenance coming up

Low-impact maintenance window

• When: Approximately once a month, on friday evening after office hours (GMT+1)
• Duration: Approximately a few hours
• Impact: Pausing of services

Periodic low-impact maintenance takes place to provide relatively small fixes, quality-of-life improvements, and security enhancements during long-term-support intervals. These moments are communicated ahead of time via the client application.

During this period the server is temporarily taken offline to process the update, resulting in a brief pause of services. Any actively running sessions will be temporarily unreachable and any calculations will be suspended.

When maintenance is completed and the server is brought back online, all paused and suspended activities will be resumed. Sessions will be restarted, maintaining the state they were in before the maintenance (including any unsaved work). Calculations will resume from the point where they were suspended.

Despite process and infrastructure being intended to resume all activities as if no interuption has taken place, it is recommended not to have unsaved work or long-running calculations with this maintenance coming up.

Emergency maintenance

• When: Acutely, with the intent to reduce impact on users where possible
• Duration: Approximately a few hours, depending on the nature of maintenance
• Impact: Pausing of services

Tygron reserves the right to conduct emergency maintenance in the event where continuity and stability of services requires it. Tygron will inform potentially affected users as soon as possible, and will include the intended start of maintenance, the estimated period of maintenance, and information for contacting Tygron for further assistance. In all cases but for emergency maintenance especially, Tygron intends to keep the period of downtime to a minimum.

During this period the server is temporarily taken offline to process the update, resulting in a brief pause of services. Any actively running sessions will be temporarily unreachable and any calculations will be suspended.

When maintenance is completed and the server is brought back online, all paused and suspended activities will be resumed. Sessions will be restarted, maintaining the state they were in before the maintenance (including any unsaved work). Calculations will resume from the point where they were suspended.

See also

• Cloud Computing
• Platform security