[geoffbarrall]

I'm having an intermittent Applescript issue with OF and even having recruited the QA folks at Omni are having trouble tracking the source of the problem down (maybe it's me?).

Basically when I run a simple activate command like -

tell application "OmniFocus" to activate

- it works fine sometimes but after a few attempts will start to abort with a "some parameter wasn't understood error". The problem seems worse if I try to embed the command in an Automator workflow. In either case it may or may not run, which is making tracking down the issue a real pain. It's almost like Applescript is caching an earlier broken version of the command from some earlier Beta of OF but I don't know enough about the internal workings of Applescript to know if this is true. For example if I load older compiled versions of Applescript for OF then it always fails first time.

Sorry if this sounds vague but it's not consistent in any way. Any help for anybody who better understands the inner workings of Applescript would be very welcome!

Screenshots - This doesn't work after a while (although does at first)



This works fine -



Many thanks.

[Lutin]

I had the same problem, so I thought about your post.

An old script was working, and suddenly showed the same error than you.

After some head scratching, it appears that Script Debugger is part of the problem.

Re-saving the script with Script Editor removed the error.

Are you using Script Debugger too?

[geoffbarrall]

Sadly no, I'm using Script Editor. Maybe if I switched to another tool it'll fix the issue although I am seeing the same problem with both Script Editor and Automator.