WorkSmart only takes 3x screenshots when frequency is set to 5x or 10x

Overview

Managers may notice that despite setting despite setting the screenshot frequency to 5x or 10x per 10-minute timecard for their direct reports, only 3 screenshots are captured per 10-minute timecard. This issue is not isolated to a single user but affects the entire team. The root cause of this problem is an infrastructure limitation, specifically regarding the maximum size of timecards, which is now set to 5MB.

This has led to the capping of the screenshot frequency at a maximum of three times (3x) per timecard, regardless of the configured frequency.

Solution

The issue with the screenshot frequency on the Crossover app is due to an infrastructure limitation. This limitation caps the screenshot frequency at a maximum of three times (3x) per timecard, regardless of the configured frequency. This change was implemented to address issues encountered by partners who experienced difficulties with timecard uploads due to the size of screenshots. Therefore, even if the frequency is configured to higher values such as five times (5x) or ten times (10x), the system will only capture three screenshots. Setting the 1x or 2x value will function as normal. 

Summary

The screenshot frequency issue in the Crossover app is due to an infrastructure limitation, which caps the screenshot frequency at 3x per timecard, regardless of the configured frequency. This change was made to address issues with timecard uploads due to large volumes of screenshots.

 

FAQ

Q: Can I increase the screenshot frequency beyond 3x per timecard?
A: No, due to an infrastructure limitation, the screenshot frequency is capped at 3x per timecard, regardless of the configured frequency.

Q: Why was this cap implemented?
A: This cap was implemented to address issues encountered by partners who experienced difficulties with timecard uploads due to the large volume of screenshots.

Q: Is this issue isolated to one individual or does it affect my entire team?
A: This issue is not isolated to a single user but affects the entire team.

Comments

0 comments

Please sign in to leave a comment.