The number that matters is the interval between closing the client and the gateway expiring its session record. With a one-session Ignition Perspective license, a quick relaunch can request session number two while the gateway still counts session number one. The visible application is closed, but the licensed slot has not yet been released. This is timing, not a bad license activation.
Common fixes that miss the timing problem
| Attempt | Why it fails or creates another problem |
|---|---|
| Close and reopen the app repeatedly | Every launch occurs while the previous gateway-side session may still occupy the only licensed slot. Repeated input does not shorten the timeout. |
Wait on the Sessions Exceeded screen |
The expired slot permits a new session request, but the already rejected launch may not become the admitted session. Close that screen and launch again after the expiration interval. |
Set the timeout to 5 seconds
|
A five-second interruption can terminate a legitimate session when the app is backgrounded or the wireless connection drops. |
| Add license capacity | Another licensed session can hide the overlap, but it does not change how long disconnected sessions remain allocated. |
| Force-close the session from the gateway | A request for this capability is tracked as IGN-2827. Treat its presence and behavior as version-dependent; check the installed gateway rather than planning around an unavailable control. |
| Add a launcher delay | A batch or shell launcher can delay reopening and display progress messages, but it only works when the delay exceeds the remaining timeout. It is an operational workaround, not session termination. |
Gateway-side session accounting
Closing a mobile client and terminating its server-side session are separate events. The gateway retains a session during a temporary communications loss so that a mobile user can move through weak wireless coverage or briefly place the application in the background without losing state. Until the gateway receives a supported termination action or the inactivity timer expires, that retained session remains part of the licensed count.
A one-session license exposes the overlap immediately:
- The iPad holds the single admitted Perspective session.
- The operator closes or backgrounds the client.
- The gateway retains that session for its configured timeout.
- The operator relaunches before expiration.
- The new connection encounters
Sessions Exceededbecause the retained session still consumes the only slot.
The relevant quantity is therefore not the number of application windows visible to the operator. It is the number of sessions the gateway still regards as active. The default session timeout stated for this configuration is 120 seconds, so a recently closed client can continue occupying the license for as long as that timer remains unexpired.
Timeout selection
Select the timeout by balancing fast slot recovery against tolerance for ordinary mobile interruptions. A range of 10 to 20 seconds was proposed for a dedicated standalone application where rapid reopening matters. A 10-second setting can still be too long when operators immediately close and relaunch, because any request inside that interval can collide with the retained session.
| Quantity or limit | Value | Where to read or set it |
|---|---|---|
| Licensed concurrent Perspective sessions |
1 in this installation |
Gateway license information |
| Default session timeout | 120 seconds |
Project Properties → Perspective → General |
| Practical starting range for rapid recovery | 10–20 seconds |
Project timeout setting, followed by a field test |
| Aggressive setting with known usability risk | 5 seconds |
Test by backgrounding the client and interrupting its network connection |
| Termination feature record | IGN-2827 |
Check the installed version and official product support information |
The shortest possible value is not automatically the best value. If operators authenticate interactively, an aggressive timeout can force another login after a brief loss of connectivity. A read-only monitoring screen may tolerate that behavior better than a workflow containing navigation state, data entry, or authenticated actions.
Project timeout procedure
- Open the affected Perspective project and record its present timeout. The stated configuration path is
Project Properties → Perspective → General. - Confirm that the license really allows only one concurrent Perspective session. If the licensed count differs, compare that count with the gateway's live Perspective sessions before changing the project.
- Set the default timeout to an initial value within
10 to 20 seconds. Use the longer end when wireless interruptions or app backgrounding are common. - Save and publish the project through the normal project workflow.
- Close the iPad application, wait longer than the configured timeout, and relaunch. The new session should be admitted after the former session expires.
- Repeat the test with progressively shorter close-to-relaunch intervals. Identify the boundary at which
Sessions Exceededappears. - Background the application and introduce a normal-duration wireless interruption. Verify that the selected value does not discard a session during ordinary use.
If operators always relaunch immediately, pair the project setting with an operating rule or controlled launcher delay. Set that delay from the measured expiration behavior, including normal gateway and network variation. A delay shorter than the timeout preserves the collision.
Verification by session state and elapsed time
Use elapsed time and gateway session status to separate licensing from connectivity. Start with no active Perspective sessions, launch the iPad application, and confirm that one session appears. Close the application while observing the Perspective session list. Time how long the record remains, then verify that it disappears near the configured expiration interval.
Next, relaunch once before expiration and once after expiration. The pre-expiration launch should reproduce the capacity message when the original record still occupies the single slot. The post-expiration launch should create one new admitted session. If the gateway shows no active session while a fresh launch still reports Sessions Exceeded, capture the gateway diagnostics and license state because the timeout model no longer explains the result.
Test backgrounding separately from fully closing the application. Mobile operating systems and intermittent wireless links can interrupt transport without expressing an immediate, clean session termination. The timeout exists to bridge that gap, so both cases belong in acceptance testing.
Recurring operational pitfalls
Operator retries can obscure the expiration boundary. Record one close time and perform one controlled relaunch per test rather than tapping repeatedly. Also distinguish the project timeout from unrelated browser, authentication, gateway, or network timers; changing the wrong timer leaves the licensed session record untouched.
A short timeout transfers failure from relaunching to continuity. Watch for unexpected logins, lost navigation context, abandoned input, and session replacement after brief wireless gaps. If those effects appear at 10 seconds, increase the value and manage rapid relaunch with an operator prompt or launcher delay.
Immediate termination from a logout event and manual termination from the gateway were identified as desired capabilities, with the gateway termination request tracked under IGN-2827. Confirm whether the installed release provides either behavior before using it in an operating procedure.
FAQ
How do I clear Ignition Perspective Sessions Exceeded?
Wait longer than the configured session timeout, close the rejected screen, and launch again. For a one-session license, the gateway must first remove the prior session from its active count.
How do I change the Perspective session timeout?
Open Project Properties → Perspective → General and change the default timeout. Start within 10 to 20 seconds, then test both rapid relaunch and normal wireless interruptions.
How do I verify that the old session has expired?
Observe the gateway's Perspective session list while timing from client closure. The old record should disappear near the configured timeout, after which a new launch should consume the single available slot.
When do I escalate Sessions Exceeded to Ignition support?
Stop reducing the timeout if ordinary app backgrounding or network loss starts terminating valid sessions. Escalate through official support when the gateway shows no active Perspective session but still rejects a new launch, or when installed-version behavior for IGN-2827 must be confirmed; provide timestamps, the configured timeout, license capacity, session-status observations, and gateway diagnostics.