TM1 Forum

Hi All,

We have a chore: start_data_import_1205am which is scheduled to execute @ 08:00 AM CET (Now 06:00 AM GMT). But whenever the there is no source data available within the scheduled time, the business users execute the chore manually.
Each time when we want to execute the process manually, the person who is about to execute the process manually… should deactivate the chore (start_data_import_1205am) and execute the same chore manually to complete the application data load process. But at this point of time while deactivating the chore…this schedule time is no more valid the time which is present in chore is ignored, once the user completed the data load process he again tries to activate the chore…here the scheduled time will be picked as the present GMT time and tries to execute the chore next day with this new time (but the user is not aware of the situation that the previous time is ignored and the new time is considered).

For better understanding please consider the below case study attached

Could you please let us know at which frequency does the time gets allocated to chore when we reactivate the chore, why is the chore ignoring the previous time and picking its own GMT time as the scheduled time when we reactivate the chore.

Thanks for your understanding.

Thanks & Regards,
Radhika

Radhika wrote: We have a chore: start_data_import_1205am which is scheduled to execute @ 08:00 AM CET (Now 06:00 AM GMT). But whenever the there is no source data available within the scheduled time, the business users execute the chore manually.
Each time when we want to execute the process manually, the person who is about to execute the process manually… should deactivate the chore (start_data_import_1205am) and execute the same chore manually to complete the application data load process. But at this point of time while deactivating the chore…this schedule time is no more valid the time which is present in chore is ignored, once the user completed the data load process he again tries to activate the chore…here the scheduled time will be picked as the present GMT time and tries to execute the chore next day with this new time (but the user is not aware of the situation that the previous time is ignored and the new time is considered).

For better understanding please consider the below case study attached

Could you please let us know at which frequency does the time gets allocated to chore when we reactivate the chore, why is the chore ignoring the previous time and picking its own GMT time as the scheduled time when we reactivate the chore.

I've really lost track of which version does what in terms of screwing up chore scheduling as a result of Applix arrogantly imposing UTC scheduling of chores rather than local time scheduling in the transition from version 7 to version 8. But most of them have their quirks.

The workaround for this is to never enter the chore scheduling page unless you absolutely, positively need to. And never do it when you're on a different day to the UTC day. Also, never do it if the start time is in a different daylight savings season to your current one. (Or at least adjust the start date so that it is in your current season.)

And in this case, you have no need to at all.

There's no reason to even deactivate the chore. Just right click on the thing to run it. It doesn't need to be deactivated for you to do that.

Thank you Alan.