Question
I’ve noticed updatedAt and updatedAtTimestamp fields on the API, yet my portal remains unchanged. What do these timestamps signify and why aren’t my updates reflected?
Based on my experience working with similar API systems, the updatedAt and updatedAtTimestamp fields generally indicate when changes were actually made on the backend, even if those changes aren’t immediately visible on the portal. It seems the portal might be relying on another process, like a cache or a secondary update mechanism, which could delay the visibility of updates. I’ve encountered similar scenarios where a backend indicator confirms an update well before a UI refresh occurs, so it’s wise to allow some processing time or check if a cache invalidation procedure needs to be run to sync the changes.
i reckon the timestamps only track backend changes. the portal might be using an old cache, hence the delay. try clearing the cache or forcing a refresh, it might just be a latency issue.