About a year ago I wrote about my new method of documenting scheduled jobs with Google Calendar. Since that article I’ve been diligently updating my calendars as jobs have been added, deleted or changed.
Earlier today I was modifying the schedule of a job when I realized my idea had a fatal flaw. I noticed some jobs were abruptly ending next week – even though their “end date” was still marked as never!
How can this be? Well, it turns out the maximum number of repeated events in GCal is 365.
One work around is to edit the job and chose to duplicate it. This has to be done job by job. The problem here is that My jobs have weren’t all created on the same date and won’t all “expire” on the same date. I really don’t want to check all the calendars daily – or even weekly – to look for jobs that appear to be ending. I guess I could just do them all as a matter of course though. Tedious, but an option.
I’m now looking for other ideas on documenting job schedules with a post over at Server Fault. Feel free to drop in and add suggestions. Maybe someone will have an idea that isn’t quite as tedious.
Possibly Related posts:
Loading tweets...
Recent Comments