Ah... yes. The functionality was updated so the update-status hook is no longer recorded in the status-log. This is by design. It was really creating undue DB load for very little value given that it is run very regularly.
I believe the flag was left on the command to continue to work against older controllers. We should update the docs.
Ah... yes. The functionality was updated so the update-status hook is no longer recorded in the status-log. This is by design. It was really creating undue DB load for very little value given that it is run very regularly.
I believe the flag was left on the command to continue to work against older controllers. We should update the docs.