[Ken Case]

We consider this urgent, and it's at the top of our priority list for 1.0.x fixes: it's entered in our internal database as <bug://bugs/44815>.

The symptoms of the problem seem to be that an action or project doesn't change state (become available or overdue) immediately on schedule, but does when you trigger a state review in some other way (e.g., by relaunching or by changing the state of a nearby item that also affects its state).

Unfortunately, we haven't been able to figure out the circumstances that cause the bug. We've reviewed the code several times and it seems correct, and we've tested it in a number of ways and can't seem to trigger the problem. Yet, as your screenshot so clearly demonstrates, the problem does exist—so there must be some essential ingredient that we're missing in our tests.

If anyone has any clues as to what might trigger this problem, we'd very much appreciate your help!