Chore not running

[appleglaze28]

Has anyone encountered any problem with their chore not working...I've set the local time to 12noon and when I checked up 12 noon, the chore didn't run at the scheduled time but when I manually run it is running. I've checked that the chore's schedule is active. Is there anything I forgot to check?

Is it possible that if the first chore was like 10 minute apart from the 2nd chore that even if the first chore hasn't complete it won't run the 2nd chore?

[Alan Kirk]

Has anyone encountered any problem with their chore not working...I've set the local time to 12noon and when I checked up 12 noon, the chore didn't run at the scheduled time but when I manually run it is running. I've checked that the chore's schedule is active. Is there anything I forgot to check?

12 noon on what schedule; Every day? Every 7 days? Every 365 days?

There are a lot of scheduling issues stemming from the ridiculous decision to inflict chore scheduling which is in UTC (GMT) rather than local time on us. For example, if you schedule a chore to run every 7 days you may, in some cases, find that although the time sets correctly, the day may be a day out. As best I recall it, this will most commonly happen if your current date is different from the UTC date when you schedule the chore. (For example, 6 hours ago it was 10:39 on the 20th of November here. However it was 23:39 on the 19th in UTC. Had I set a 7 day chore at that time, it would most likely have been set on the wrong date.)

In other cases if you set the start date to a date after you're due to move on or off daylight savings, the chore schedule may be an hour out.

The exact amount of bugginess can vary by version and by the specifics of the settings. However if the chore is active but still doesn't run, the odds are that when you check the "GMT time" in the chore wizard and compare it to what the UTC really was was at noon your time, the two won't be the same.

You can usually avoid the problem by:
- Making sure that the chore start time is in the same daylight savings season that you're in;
- Making sure that the UTC date is the same as your own date when you create a chore. In our case that means that we don't create a schedule until 10 or 11am, depending on the season.

[appleglaze28]

I tried resetting the time making sure that the UTC is the same day as the local and I still having issues with the chore running...I don't think my TI has a problem since when I manually run the TI processes they run perfectly. I tried re-creating the chore and its still not working and they the schedules are activated.

[Alan Kirk]

I tried re-setting the time making sure that the UTC is the same day as the local and I still having issues with the chore running...I don't think my TI has a problem since when I manually run the TI processes they run perfectly. I tried re-creating the chore and its still not working and they the schedules are activated.

I suggest that you post a copy of the relevant .cho file from your data directory.

I think you're GMT+8 hours from memory, presumably not on daylight savings time at the moment since you're in the northern hemisphere?

[appleglaze28]

I was wondering I'm still having an issue about the chores not running. I tried re-installing TM1 on my server(technically its a virtual server but we're moving to actual one once I finished development). Anyway I encountered during installation an error "UNABLE TO READ FILE" but the installation didn't roll back and I was wondering if there's a file that was not read that's causing my problem with the chore not running.

I have no more issue with the timezone cause I tried it and it was working one day then when I logged back in the next day that i set to run at around 5am in the morning when I got to work and logged on none of the data loaded in all cubes. I thought maybe there was an error in running the chore but when I manually ran it, it ran perfectly.

I know for TM1 9.4 Server 2008 is not compatible or supported but it has been the same OS before it was running perfectly for the past 2 months before this problem came up.