Maintenance: Difference between revisions

From Tygron Support wiki
Jump to navigation Jump to search
← Older edit
Maxim@tygron.com (talk | contribs)
Tygron, Tygron_admin, Bureaucrats, Interface administrators, Administrators
6,622 edits
No edit summary
No edit summary
 
(13 intermediate revisions by the same user not shown)
Line 1: Line 1:
The {{software}} 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.
The {{software}} undergoes continuous development and improvements, to improve and expand the user experience and/or make security enhancements. To make this possible, moments of maintenance are instituted during which service may be limited.


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.
==Maintenance Window==
These maintenance windows are communicated ahead of time via:
* The headlines panel in the client [[Main Menu]].
* In the upper right corner of the Editor [[Ribbon]].  
* When the window is close the user will also get a popup panel indicating the approaching window.


==Large maintenance window==
It is also possible to get the window period via API endpoint: https://engine.tygron.com/maintenance (time in milliseconds of start and end of 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 {{software}}. These moments are communicated ahead of time via the client application, and via pro-active newsletters starting 2 months ahead of the release.
==Types==
There are several types of maintenance.


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.
===Hot-fixes===
* '''When''': When needed, mostly in the evenings
* '''Duration''': No downtime
* '''Impact''': No Pausing of services


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.
Hot-fixes can be applied directly to the [[Client]] application and have no impact on the User workflow. When the user restart the client will automatically update itself. They can also be applied to [[GPU]] servers, in this case the server will shortly show up in status 'maintenance' in the [[Calculation panel]].


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===
 
* '''When''': Approximately once a month, on Friday evening 20:00 (GMT+1)
==Low-impact maintenance window==
* '''Duration''': Approximately one hour
* '''When''': Approximately once a month, on friday evening after office hours (GMT+1)
* '''Duration''': Approximately a few hours
* '''Impact''': Pausing of services
* '''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.
Periodic low-impact maintenance takes place to provide relatively small fixes, quality-of-life improvements, and security enhancements during long-term-support intervals.  


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.
===Emergencies===
* '''When''': Acutely, with the intent to reduce impact on users where possible
* '''Duration''': Approximately one hour
* '''Impact''': Pausing of services


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.
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. Tygron intends to minimize downtime in all cases, including during emergency maintenance.


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.
===Major LTS Update===
* '''When''': Approximately once every two years (see [[Roadmap]]), on Friday evening 20:00 (GMT+1)
* '''Duration''': Approximately a day
* '''Impact''': Pausing of services


==Emergency maintenance==
Major LTS updates take place as part of the [[Roadmap]] to release 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 {{software}}. These moments are communicated ahead of time via the client application, and via pro-active newsletters starting 2 months ahead of the release. New functionality can be tested on the [[Roadmap#Preview|Preview]] server.
* '''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.
==Update Process (except for hot-fixes)==


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.
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.
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 interruption has taken place, it is ''recommended'' not to have unsaved work or long-running calculations with this maintenance coming up.


{{article end
{{article end

Latest revision as of 16:10, 13 October 2026

The Tygron Platform undergoes continuous development and improvements, to improve and expand the user experience and/or make security enhancements. To make this possible, moments of maintenance are instituted during which service may be limited.

Maintenance Window

These maintenance windows are communicated ahead of time via:

  • The headlines panel in the client Main Menu.
  • In the upper right corner of the Editor Ribbon.
  • When the window is close the user will also get a popup panel indicating the approaching window.

It is also possible to get the window period via API endpoint: https://engine.tygron.com/maintenance (time in milliseconds of start and end of maintenance window).

Types

There are several types of maintenance.

Hot-fixes

  • When: When needed, mostly in the evenings
  • Duration: No downtime
  • Impact: No Pausing of services

Hot-fixes can be applied directly to the Client application and have no impact on the User workflow. When the user restart the client will automatically update itself. They can also be applied to GPU servers, in this case the server will shortly show up in status 'maintenance' in the Calculation panel.

Low-impact

  • When: Approximately once a month, on Friday evening 20:00 (GMT+1)
  • Duration: Approximately one hour
  • 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.

Emergencies

  • When: Acutely, with the intent to reduce impact on users where possible
  • Duration: Approximately one hour
  • 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. Tygron intends to minimize downtime in all cases, including during emergency maintenance.

Major LTS Update

  • When: Approximately once every two years (see Roadmap), on Friday evening 20:00 (GMT+1)
  • Duration: Approximately a day
  • Impact: Pausing of services

Major LTS updates take place as part of the Roadmap to release 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. New functionality can be tested on the Preview server.

Update Process (except for hot-fixes)

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 interruption has taken place, it is recommended not to have unsaved work or long-running calculations with this maintenance coming up.

See also

Retrieved from "https://support.tygron.com/w/index.php?title=Maintenance&oldid=95651"