Comment 4 for bug 2063087

I dug into this further.

Juju's behaviour around hooks and visible data is deliberate.

If we notify via hook emission of changing data, that data should remain the same each time you read it, until we tell you it has changed again.

This is to provide idempotency around hook executions, and to eliminate potential charm behaviour of polling Juju in hook handlers waiting for data that may change.

The links I posted above indicate the behaviour for *application* relation data is incorrect and *not* vice-versa.

We do not intend to undertake a fix for the unit relation data that you have observed.