Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

cudaboy_71

macrumors newbie
Original poster
Dec 7, 2002
7
0
sacramento, ca
[SOLVED!]
this is a production machine. So, I can't easily upgrade this past El Capitan (10.11.6); and not really willing to go through the upgrade process to just test if this single issue is resolved.

So, with that out of the way, I have an applescript application that needs to run every two weeks. What I've always done in the past is set up a repeating calendar event. And, under 'alert', I change it to 'custom'; open file; and other; and choose the applescript application to run.

For the first run of the event, everything is fine. But, the repeated events are always set to 'none'. And, even when I edit the next scheduled event and add the applescript application to it; and I confirm 'all future events', the future events are always set to 'none'.

Also, the script immediately runs when I save the event even though it is set in the future.

This used to work even as far back as iCal. Is this a known bug? am I doing something wrong? Is there a better app to get this to run on schedule and I can just forget about calendar.app? Calendar has always been easy to configure and it was reliable. But, I don't really care how it runs--just that it runs.
 
Last edited:
just doing a little digging. It looks like the setting to run the external application gets wiped when the event is opened. See the video. The setting is initially there when the event is reopened after creation, but almost immediately gets wiped back to None.


I have another test set up now to see if it runs properly the on subsequent events if the event is not opened after being cretaed. But, I don't see a way to get an event repeated more frequently than once a day. So, I'll know more tomorrow (or more like Friday, next time I'm on this computer)

As a further bit of testing, the script was originally stored on a volume other than the boot volume. I tried scheduling the event for a file on the boot volume with no change in behavior.
 
PAYDIRT! Mark it solved.

The issue is with iCloud syncing. The solution is to create a local calendar. This is not as easy as it sounds. I went to the file menu and selected 'new calendar' and a flyout menu offered 'iCloud' and no other option. That's not going to fix it.

So, I right-clicked in the blank area below the list of active calendars in the sidebar and selected 'new calendar'. Note: the sidebar may not be on by default--to resolve go to View-->show calendar list

Next, the New Calendar showed up as 'Untitled' under the iCloud calendars. But, I couldn't delete it either. On a hunch, I quit Calendar and restarted the app. Lo and behold, now the calendar shows in its own On my mac list above the iCloud calendars.

I created my scheduled script in this new, aptly named 'local scripts' calendar and the settings stick. I didn't even bother running a daily test. I'll know if 2 weeks if this works when my script either runs, or doesn't. But, based on the settings now showing correctly in the event, I'm 95% confident it will work as advertised now.

Special thanks to cudaboy_71 for all his help with this. </smug>
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.