Clarity Reporting - Known Issues

Known issues and quirks related to the Clarity Report writer

An issue appearing in this list does not guarantee development priority. If you are having issues caused by a known issue please have your implementation partner raise a case referencing the issue ID.

Clarity run as an automated/unattended command line application occasionally freezing.

Issue ID: EXB-6575

When Clarity is run unheaded (as a command line app from a command line call) it is vulnerable to any prompts that would normally appear on screen blocking it.

This means if Clarity encountered a request for input, or there is any kind of error prompt reported, the session will appear to hang (as it will remain open with that error “displayed” to its application session.

This isn’t an issue when running Clarity directly as a user, but can be an issue if Clarity is being called from an automated process on a server.

Workaround:
Using ClarityRT.exe will generally be more stable.

If calling Clarity as an automated process, it is recommended to use a wrapping process so you can terminate any sessions that get stuck.