Connect lease periods and offline use
In the event of an internet outage, failed connection, or other scenario where a Connect-licensed product is disconnected or otherwise working in an offline mode, the product will behave depending on the nature of the scenario.
General Description |
Example |
Impact |
Prerequisites |
|---|---|---|---|
|
Client open, unable to connect Winshuttle client application is open, but the connection to Winshuttle Connect is lost. |
This might occur when you are logged into and working with a Winshuttle client application (Studio, Transaction, Query, etc.). | You can continue to work in offline mode for 72 hours | None |
|
Client not open, unable to connect Winshuttle client application has not been opened yet, and you cannot connect to Winshuttle Connect. |
This might occur if Winshuttle Connect is down prior to opening and logging in to your client application (Studio, Transaction, Query etc.). | You can continue to work in offline mode for 72 hours |
|
|
Client opened and then exited, unable to connect The Winshuttle client application was working and then shut down, and you cannot connect to Winshuttle Connect. |
This might occur when you are logged into and working with a Winshuttle client application (Studio, Transaction, Query, etc.), exit the application, and then lose internet connectivity so you can't connect to Winshuttle Connect. | You can continue to work in offline mode for a cumulative 6 hours lease | None |
|
Client has not been opened, no internet connection. The Winshuttle client application has not been opened or used recently, and there is no Internet connection. |
This might occur in you have no Internet connection and have not recently opened or used a Winshuttle client application (Studio, Transaction, Query, etc.). | You can continue to work in offline mode for a cumulative 6 hours lease |
|