Expired Sessions

Sessions that are not completed can now be expired within a pre-defined time frame. An expired session cannot be processed any further, preventing any potential miss-use or late inspections.

How 'Expired Sessions' Works

  1. Select the desired timeframe beyond which incomplete sessions will be set to expire, as shown below.

This can be configured at an API Key level for a new or existing API Key

  1. Once a session expires, it will be visualized on the dashboard as shown below.

A session will expire if it is not in COMPLETE stage (i.e. is still in IDLE, STARTED, or PROCESS stage) when the chosen time frame is reached

  1. For an expired session, the inspection link when opened returns an error message, 'The requested Session Key has already expired' and no further inspection is possible.

Last updated