Have you seen your achievements yet? We noticed traffic toward the page and discovered it’s broken since the time we upgraded our system framework.
It’s now back and working again. See your bonuses and promotions! You deserve it! 🙂
If you have any questions please let us know by clicking here
We are improving attendance resolution by removing a mis-understood feature, attendance adjustments.
This is an old feature that is in conflict with the normal attendance resolution. If you do not know what it is don’t worry you wouldn’t miss it.
It’s essentially a contradiction to the attendance resolution. Let’s say
Trying to generate payroll for Salaried employees that had unresolved attendance was previously blocked. We have now fixed the issue and at the same time maintained this unintended behaviour to help transition some clients that may have been using the Salary pay mode incorrectly for some employees.
If you have
The engineering team made a series of fixes to rollcall days…
Duplicate rollcall days are now impossible in the database. (Exact same shift or paid day off attached to a roll call day)
The source of duplicates has been eliminated by using a resource (redis) locking mechanism.
-Bram Whillock
Last July 31, 2015, we were affected by an AWS outage that caused a lot of issues with our services, including clockings.
Although we were able to recover and replay clockings that were done through TeamClock Android, iOS and Chrome right away, we weren’t able to recover clockings done through
On August 3, 2015 we were alerted that the system was not generating absence attendance records correctly. During our investigation we ended up realizing that this was an un-noticed after effect of the outage from July 31 .
We learned that when Amazon went down it left a locking mechanism that
Last July 31, 2015, we were affected by an outage from Amazon Web Services (AWS). A lot of our backend services were affected like generating reports and sending clockings.
Around 1:06pm SGT we started getting elevated error rates from the AWS API. The root cause as described by our
Web attendance analytics now consistently uses actual clocking data rather than the resolved clocking information. This allows the feature to be the basis for attendance incentives. Before this would not be possible due to the fact that managers has the prerogative to give grace when a employee is late. Now
We found out the attendance report is mostly used by TAS (Time, Attendance and Scheduling) accounts and is rarely used by Payroll accounts. In response to this findings we are cleaning up unneeded feature to give a cleaner interface and provide better support.
If you have any questions please let
We’ve notice that users are constantly confused about how the undertime rule works when one sets it to sum work hours.
It was designed to do one thing which is to count hours worked beyond what the employee is scheduled to work. An example scenario would be:
John work 9am