Suddenly all the scheduled reports runs with a delay of one hour.
Does this have anything to do with daylight savings?
The environment is: Crystal Report Server 2008, Tomcat and Business Objects Enterprise 12.0
Detail: This started to happen last weekend,when the Brazilian daylight saving was supposed to end. The server wrongly adjusted the time to end of the daylight saving.
(Here the dates of daylight savings are not default (E.g: Starts third Saturday of October, ends second Saturday of February). Due to politics reason this changes every year).
Anyway, we set the timezone again to daylight saving (which actually is going to end February 17 - this weekend). Restarted the server, but on Crystal Management Console all the reports are wrongly scheduled with +1hour. (E.g: If the report is supposed to be delivered at 12:00 PM, it's doing on 1:00 PM)
Has anyone came across this issue? I did not find anything relevant to my problem on web researches; is there a workaround for this issue? Any time zone configuration that should be made (where?) ?
Any help would be appreciated.
After the timezone ended, the schedulling reports runned on the right time again. Crystal Server had a delay in adjusting the time,because it does only when the server is idle.
Related
I have some tumbling window triggers that are set to run at specific intervals 6 hours apart. They need to run at a designated time (think 5am and 11am, and so on) I have them set up so that they are self-dependent and dependent on a connection check trigger.
The problem arises when daylight savings comes around. Tumbling window triggers only work in UTC and when the clock changes in our time zone, the times they are triggered change by an hour (forward or back depending on the time of year). This causes data to be late to its destination and I am forced to manually deploy new triggers around daylight savings time.
I am wondering if there is a better way to work around daylight savings time as Tumbling Window Triggers do not support any time zone other than UTC and deploying new triggers every time is not an effective solution.
Not sure if I understand your requirement, it is actually different between 6 hours apart and setting scheduled triggers for 2 designated times which are 6 hours apart.
If you want to schedule the job for every 6 hours, the timezone should have no impact since the trigger should always trigger every 6 hours. This is the correct use case for tumbling window trigger.
If you want to schedule for designated times, you should go for scheduled trigger, which supports for timezones. For catering daylight saving time, you can simply select the timezone you want, ADF will auto adjust according to daylight saving time as specified in the UI.
I'm getting this message when I'm trying to access a file which is in my OneDrive
through a link to this file. It happens for 2 hours , between 20:00 and 22:00 h Eastern European Time .Has anybody had the same problem and is it continuing to happen during a long period of time(days , months ,years)?
I am trying to write a periodic cron task for celery which should execute every hour from Tuesday 12pm to Wednesday 12 pm. That is a 24 hour period but spans two different days. Is it possible to schedule this as a single task like
#periodic_task(run_every=crontab(<an expression equivalent to stated above>))
At the moment I am writing two tasks: one with decorator:
crontab(minute='0',hour='12-23',day_of_week='tue') and another with
crontab(minute='0',hour='0-11',day_of_week='wed')
Some examples are given here
Thanks
Unfortunately the two specifications you've created cannot be consolidated into the same rule. The only real solution (less than ideal in most scenarios) that I can think of is to change the timezone under which Celery is executing using CELERY_TIMEZONE. +/-12 hours from the timezone you currently have configured with Celery would do the trick, though there very obviously could be other ramifications to doing this.
I am accessing an API hosted by Mashery with the following rate limit:
5 calls per second
10,000 calls per day
Does that imply that I can make 10,000 requests at 6:00PM, and then make another 10,000 requests at midnight? Or, does it mean I can only make 10,000 requests within any 24-hour period?
For example, does it mean that if I make 10,000 requests between 6:00PM one day, and 6:00PM the next, that I have to wait until 6:00:01PM before I can make another request. And then, at most I can make requests at the same rate I made the day prior (as the 24-hour period continuously shifts)?
I apologize if this is off-topic. I have a support request in for clarification, but I don't think they'll get back to me any time soon, and I figured that someone here would be familiar with the limits.
The limit is set per Calendar date and resets every midnight GMT time.
So for example if you made 10,000 calls at 6pm pacific (which is 2am GMT) you would have to wait 22 hours until 4pm pacific (which is midnight GMT) until you can start using your next batch of 10,000 daily calls.
Hope that answers your question.
Thanks,
Shai Simchi
Mashery Customer Support
I'm currently developing a internal application for a company that does patient transport between hospitals and doctor's offices. The module that I'm working on now will give the company the ability to track their various vehicle maintenance expenses and services performed as well as give them the ability to schedule different maintenance services for each vehicle in their fleet.
Different types of maintenance are performed at different time intervals. These are to be repeating events. Some are to be repeated weekly, some monthly, and others every three months.
For the maintenance events that repeat on a monthly or semi-monthly basis I'm a little unsure how I should go about determining days in future months that a event should be scheduled if the date is late in the month and that particular day does not exist a in a subsequent month.
For example, if I schedule a event on January 31st that is to be repeated monthly then I'm unsure where in February that event should be assigned. I would appreciate any suggestions from anyone who has developed a scheduling application detailing how you accounted for these types of scheduling problems.
Looks like I jumped the gun asking this question. I decided to see how Google Calendar handles monthly recurring events. If I add a event for January 31st 2012 and set it as a recurring event then I am given the option to have that event repeat every month that has day 31 or to repeat the last Tuesday of each month.
In my case it would be best to have the event repeat the last Tuesday of each month because the vehicle maintenance shop is closed on Sundays and the maintenance cannot skip a month just because that particular day did not exist in each month.