TimeTrex Time and Attendance

has there been anything back from the dev's on the oringal issue of this post.

is there a way to make it so an employee can't clock out with not having a clock in. I believe I have users who are changing the clock into the clock out and it's going through. for example today we have a user who only had a clock out it was the first ever clock in / clock out.

ahh ok so the who's in /out dashboard will only provide a listing of the days in/out ounce that end of time for the day hits then you have to wait for the exceptions to pick it up.

so my understanding of who in/out should show a live feed of who's still punched in and who's punched out. as you can see melissa and Jenna are currently missing a punch out which would mean they are still technically punched in but not showing on the who's in who's out so we are unable to determine...

please see attachments for more info

my other question on this would be why would people being listed under exceptions as hasn't clocked out but not showing under the who's in/out. right now there are two people who haven't clocked out and are listed under the exceptions dashboard. but not under the who's in/out dashboard.

below shows user Test with a punch in and a punch out but still shown as logged in.

i agree what that would make life easier

ok, I was able to recreate this issue but not sure how this issue first started.

if an employee doesn't have a time in but they have an out time. when you go to add there in time they remain as if they are clocked in even though they have a time in and a time out.

I'm not sure if I will be able to or not that was kinda of a strange bug. I will try a few attempts different ways see if I can reproduce the error

ok thankyou.

hi looking at the time trex dashboard there is a view by default named exceptions (subordinates) this list employees first name|last name|date|serverity|exception|code . now the odd issue I'm seeing with this is that employees with the exception missing in or missing out don't show up for 2 days. so...

let me rephrase this if it wasn't clear what I was asking 1. on the timetrex dashboard looking at the who's in / out we had an employee who we had to clock in for her. she was able to clock out with using her account. 2. later that day we were looking at the who's in/out dashboard she was shown as s...

today we have an employee we had to clock in she clocked herself out at the end of the day. when we were looking at the who's in/out dashboard it was still showing her as clocked in I had to remove all time clock information for today and manually enter the time in in order to clear her from the who...

what we have done was enforce a 2222 password requirements 2 upper case 2 lower case 2 numbers 2 special characters it's the only thing I have seen that no matter what the password is it will always work from previous talks the password requirements are only going to increase. what we do is have new...

so without the logs any idea what could have caused the import to fail?

that would make sense not sure why I didn't get any logs from yesterday when we had people in and out and the CSV export. i guess i will continue to monitor it if it happens again i will send the logs and re-open this topic on what caused it to not work.

yea I'm running it every minute as it stands right now just wasn't sure if that was correct.

ok maybe its just delayed on the logs then i will keep an eye out as the day goes on

how often should you run the cron.php I thinking I'm doing it to often right now I wanted to see what is the recommended time between running cron.php

so looking at the logs I didn't get the log information. needed or anything from that day if I disabled buffer_output because I'm getting a lot of useless information in the logs but I guess I will prob need to turn that back b/c I'm not getting the logs I need. my current log setting is setting are...

hi, yesterday we went to import our CSV like we do every day. we get our 13 errors from passwords that we expect because people's password that no longer meets the password requirements then when we get to step 6 it was error out saying that 200+ records where invalid reason was the id number now th...

i guess this kinda falls under that but not really. its the user setting there password to a csv file that gets uploaded through the import feature. but it doesn't do it to every new account made that way just some. then with no changes to a user account it makes them change it for no reason. i knew...

hi im currently running timetrex v9.1.3 all employees are added into timetrex through a imported csv file lately since we have upgraded to the v9.1.3 we been having an issue when a new employee's account is set up the next time when they go to log in its prompting for password change it will also do...

ok i will do that thankyou