Schedules issue
-
- Posts: 18
- Joined: Fri May 21, 2010 11:48 pm
Schedules issue
Hi, I created a recurring template in the schedules, I set 2 of our employess on that template, and now when ever I go to schedules, it looks as if the system as copied that schedule and put it in each hour the schedule is active, there are currently 9 Pages of that schedule listed under scheduled shifts, I delete them all, and they start adding up and accruing again. How can I fix this so it only shows it once?
Re: Schedules issue
Please post a screenshot of the Schedule -> MySchedule page showing the problem, as well as your recurring schedule template.
-
- Posts: 18
- Joined: Fri May 21, 2010 11:48 pm
Re: Schedules issue
here is the my schedules page
Here is the schedules shifts:
here is the template:
Let me know if you need anything else, Thanks
Here is the schedules shifts:
here is the template:
Let me know if you need anything else, Thanks
Re: Schedules issue
You didn't show any actual scheduled shifts in your Schedule -> MySchedule screenshot. Please change the view to "Weekly" and post a screenshot of that.
-
- Posts: 18
- Joined: Fri May 21, 2010 11:48 pm
Re: Schedules issue
here is the weekly schedule
Re: Schedules issue
The Schedule -> MySchedule page looks fine, I don't see any problems with it. However Schedule -> Scheduled Shifts definitely doesn't look correct, which is strange since they both basically use the same source data.
What version of TimeTrex are you using and with what database?
What version of TimeTrex are you using and with what database?
-
- Posts: 18
- Joined: Fri May 21, 2010 11:48 pm
Re: Schedules issue
We are using Mysql 5.0 and, Version of Time Trex is 3.0.8
Re: Schedules issue
Please upgrade to the latest version of TimeTrex and let us know if the problem persists.
Re: Schedules issue
Actually, under Schedule -> Scheduled Shifts, can you copy and paste the URL of the first five "Edit" links on May 26th here?
-
- Posts: 18
- Joined: Fri May 21, 2010 11:48 pm
Re: Schedules issue
sure here they are:
javascript:TIMETREX.schedule.editSchedule(621)
javascript:TIMETREX.schedule.editSchedule(615)
javascript:TIMETREX.schedule.editSchedule(617)
javascript:TIMETREX.schedule.editSchedule(619)
javascript:TIMETREX.schedule.editSchedule(623)
javascript:TIMETREX.schedule.editSchedule(621)
javascript:TIMETREX.schedule.editSchedule(615)
javascript:TIMETREX.schedule.editSchedule(617)
javascript:TIMETREX.schedule.editSchedule(619)
javascript:TIMETREX.schedule.editSchedule(623)
-
- Posts: 18
- Joined: Fri May 21, 2010 11:48 pm
Re: Schedules issue
sorry wrong date, here they are:
javascript:TIMETREX.schedule.editSchedule(570)
javascript:TIMETREX.schedule.editSchedule(569)
javascript:TIMETREX.schedule.editSchedule(568)
javascript:TIMETREX.schedule.editSchedule(567)
javascript:TIMETREX.schedule.editSchedule(566)
javascript:TIMETREX.schedule.editSchedule(570)
javascript:TIMETREX.schedule.editSchedule(569)
javascript:TIMETREX.schedule.editSchedule(568)
javascript:TIMETREX.schedule.editSchedule(567)
javascript:TIMETREX.schedule.editSchedule(566)
Re: Schedules issue
I talked to the developers regarding this, and it appears to be an issue that only occurs on MySQL that is causing TimeTrex to continually add duplicate scheduled shifts every hour.
This issue will be fixed in v3.1.1 of TimeTrex which should be available sometime in the next week or so, in the mean time I would recommend removing employees from recurring schedules under Schedule -> Recurring Schedule and manually schedule them with Schedule -> Mass Schedule instead.
Of course another option would be to switch to using PostgreSQL, which is faster and much more stable (especially in this regard) than MySQL.
This issue will be fixed in v3.1.1 of TimeTrex which should be available sometime in the next week or so, in the mean time I would recommend removing employees from recurring schedules under Schedule -> Recurring Schedule and manually schedule them with Schedule -> Mass Schedule instead.
Of course another option would be to switch to using PostgreSQL, which is faster and much more stable (especially in this regard) than MySQL.