Keep Alive - Revision history

Rudolf@tygron.nl: Rudolf@tygron.nl moved page Keep alive to Keep Alive without leaving a redirect: Capitalization fix

2026-04-23T11:51:39Z

Rudolf@tygron.nl moved page Keep alive to Keep Alive without leaving a redirect: Capitalization fix

← Older revision	Revision as of 11:51, 23 April 2026
(No difference)

Vincent@tygron.nl at 16:04, 13 January 2026

2026-01-13T16:04:31Z

← Older revision		Revision as of 16:04, 13 January 2026
Line 9:		Line 9:
	* To finalize a long [[calculation]]. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automatically set to Keep Alive, and the user can exit while the calculation continues on the server, at the designated times.		* To finalize a long [[calculation]]. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automatically set to Keep Alive, and the user can exit while the calculation continues on the server, at the designated times.

	After 7 days, the Keep Alive option is ended automatically. ~~An exception is made~~ for [https://www.tygron.com/~~roadmap~~/ ~~Partners~~].		After 7 days, the Keep Alive option is ended automatically. If you like to use this option for a longer period, please contact us with our [https://www.tygron.com/nl/contact/ contact form].

	==How to use the Keep Alive option==		==How to use the Keep Alive option==

Hedi@tygron.com at 09:47, 4 May 2023

2023-05-04T09:47:24Z

← Older revision		Revision as of 09:47, 4 May 2023
Line 9:		Line 9:
	* To finalize a long [[calculation]]. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automatically set to Keep Alive, and the user can exit while the calculation continues on the server, at the designated times.		* To finalize a long [[calculation]]. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automatically set to Keep Alive, and the user can exit while the calculation continues on the server, at the designated times.

	After 7 days, the Keep Alive option is ended automatically. An exception is made for [https://www.tygron.com/roadmap/ Partners]		After 7 days, the Keep Alive option is ended automatically. An exception is made for [https://www.tygron.com/roadmap/ Partners].

	==How to use the Keep Alive option==		==How to use the Keep Alive option==

Hedi@tygron.com at 09:47, 4 May 2023

2023-05-04T09:47:15Z

← Older revision		Revision as of 09:47, 4 May 2023
Line 9:		Line 9:
	* To finalize a long [[calculation]]. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automatically set to Keep Alive, and the user can exit while the calculation continues on the server, at the designated times.		* To finalize a long [[calculation]]. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automatically set to Keep Alive, and the user can exit while the calculation continues on the server, at the designated times.

	After 7 days, the Keep Alive option is ended automatically. An exception is made for ~~Partners, also see~~ https://www.tygron.com/roadmap/		After 7 days, the Keep Alive option is ended automatically. An exception is made for [https://www.tygron.com/roadmap/ Partners]

	==How to use the Keep Alive option==		==How to use the Keep Alive option==

Hedi@tygron.com at 09:45, 4 May 2023

2023-05-04T09:45:23Z

← Older revision		Revision as of 09:45, 4 May 2023
Line 3:		Line 3:
	There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is commonly used in the following use cases:		There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is commonly used in the following use cases:

	* For other users to be able to join. The Keep Alive option enables the project to be accessed by users with 'join only' [[Account_management\|access rights]]. This can be implemented in a (multi user) stakeholder [[~~impact~~ session]], where an organization has a session running, and is inviting external stakeholders (civilians, companies, municipalities, etc) to join the session on the {{software}}.		* For other users to be able to join. The Keep Alive option enables the project to be accessed by users with 'join only' [[Account_management\|access rights]]. This can be implemented in a (multi user) stakeholder [[session]], where an organization has a session running, and is inviting external stakeholders (civilians, companies, municipalities, etc) to join the session on the {{software}}.

	* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.		* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.

Hedi@tygron.com at 09:44, 4 May 2023

2023-05-04T09:44:34Z

← Older revision		Revision as of 09:44, 4 May 2023
Line 3:		Line 3:
	There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is commonly used in the following use cases:		There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is commonly used in the following use cases:

	* For other users to be able to join. The Keep Alive option enables the project to be accessed by users with 'join only' [[access rights~~\|Account_management~~]]. This can be implemented in a (multi user) stakeholder [[impact session]], where an organization has a session running, and is inviting external stakeholders (civilians, companies, municipalities, etc) to join the session on the {{software}}.		* For other users to be able to join. The Keep Alive option enables the project to be accessed by users with 'join only' [[Account_management\|access rights]]. This can be implemented in a (multi user) stakeholder [[impact session]], where an organization has a session running, and is inviting external stakeholders (civilians, companies, municipalities, etc) to join the session on the {{software}}.

	* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.		* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.

Hedi@tygron.com at 09:44, 4 May 2023

2023-05-04T09:44:13Z

← Older revision		Revision as of 09:44, 4 May 2023
Line 3:		Line 3:
	There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is commonly used in the following use cases:		There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is commonly used in the following use cases:

	* For other users to be able to join. The Keep Alive option enables the project to be accessed by users with 'join only' [[access rights]]. This can be implemented in a (multi user) stakeholder [[impact session]], where an organization has a session running, and is inviting external stakeholders (civilians, companies, municipalities, etc) to join the session on the {{software}}.		* For other users to be able to join. The Keep Alive option enables the project to be accessed by users with 'join only' [[access rights\|Account_management]]. This can be implemented in a (multi user) stakeholder [[impact session]], where an organization has a session running, and is inviting external stakeholders (civilians, companies, municipalities, etc) to join the session on the {{software}}.

	* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.		* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.

Hedi@tygron.com at 09:40, 4 May 2023

2023-05-04T09:40:46Z

← Older revision		Revision as of 09:40, 4 May 2023
Line 8:		Line 8:

	* To finalize a long [[calculation]]. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automatically set to Keep Alive, and the user can exit while the calculation continues on the server, at the designated times.		* To finalize a long [[calculation]]. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automatically set to Keep Alive, and the user can exit while the calculation continues on the server, at the designated times.

			After 7 days, the Keep Alive option is ended automatically. An exception is made for Partners, also see https://www.tygron.com/roadmap/

	==How to use the Keep Alive option==		==How to use the Keep Alive option==

Hedi@tygron.com at 09:34, 4 May 2023

2023-05-04T09:34:12Z

← Older revision		Revision as of 09:34, 4 May 2023
Line 3:		Line 3:
	There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is commonly used in the following use cases:		There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is commonly used in the following use cases:

	* For other users to be able to join. ~~This~~ enables the project to be accessed by users with ~~only~~ join only access rights. This can be implemented in a (multi user) stakeholder [[impact session]], where an organization has a session running, and is inviting external stakeholders (civilians. companies, municipalities, etc) to join the session on the {{software}}.		* For other users to be able to join. The Keep Alive option enables the project to be accessed by users with 'join only' [[access rights]]. This can be implemented in a (multi user) stakeholder [[impact session]], where an organization has a session running, and is inviting external stakeholders (civilians, companies, municipalities, etc) to join the session on the {{software}}.

	* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.		* To complete the process of uploading data from a service. Some services contain a large amount of (3D) data. Having the session continue to process this data in the background will free up a user's time and system. Please note that in case the data is located at the user's system, this option does not work as described, as the session needs to be open on the system where the local data is located.

	* To finalize a long [[calculation]]. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automatically set to Keep Alive, and the user can exit. while the calculation continues on the server, at the designated times.		* To finalize a long [[calculation]]. Some calculations can take a long time. It is possible to schedule such calculations with a long scheduled update. When this is selected, the session is automatically set to Keep Alive, and the user can exit while the calculation continues on the server, at the designated times.

	==How to use the Keep Alive option==		==How to use the Keep Alive option==

Frank@tygron.nl at 12:28, 27 February 2023

2023-02-27T12:28:41Z

← Older revision		Revision as of 12:28, 27 February 2023
Line 1:		Line 1:
	The Keep Alive option can be found in the [[File Menu]] of a [[project]] in the [[editor]] and is an option to keep a [[session]] running on the [[server]], a so called Keep Alive session, even after the [[client]] is closed. The keep alive mode delays an automatic shut-down of your project session due to a [[time-out]].		The Keep Alive option can be found in the [[File Menu]] of a [[project]] in the [[editor]] and is an option to keep a [[session]] running on the {{software\|server}}, a so called Keep Alive session, even after the [[client]] is closed. The keep alive mode delays an automatic shut-down of your project session due to a [[time-out]].

	There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is commonly used in the following use cases:		There are a couple of scenarios where keeping a session alive in the {{software}} is desirable. This option is commonly used in the following use cases: