I’m sure there’s an explanation for this, but on it’s face, it’s a bit confusing.
if i write to a page prop (urlParams in this case) from a client (browser/designer/presumably workspace), the associated timestamp is derived from the gateway
if i write to a session/view/component prop, the associated timestamp is derived from the client
I don't see why that is surprising. URL parameters are "bare" where they are received, at the gateway, so naturally will get the gateway's UTC timestamp on their qualified values. Whereas, for any operation involving the browser or designer, those can construct and send qualified values themselves, so would have the UTC timestamp where they were constructed.
(Unless you have non-timezone skew from real time, the difference should be effectively zero. Timestamps in QVs are UTC.)
Not necessarily surprising, given the “read only” use-case assumption, just confusing since they can be written to from designer/browser. In that case, I’d assume the “normal” behavior would apply.
Does your designer's time differ from the gateway (after converting both to UTC)?
lol, that’s precisely how I discovered it.