It was like that all morning. I waited a while for the script to fire before unlocking but nothing happened. Like I said, a reboot cured it and I haven't seen this behaviour after that. If I see it again, do you have any suggestions what information to collect?

A completely different question:

I started writing a simple dbus listener in python which listens to dbus messages from the timed daemon and updates a profilematic rule's activation time or active status according to the message.

I wanted to know if using the updateRule method this way would have any adverse effects?