when adding new value in Node custom property it takes a day to display in application , what is the root cause for such a problem ?
NPM 2025.4.1
Do you have an additional web server? If so, do you have the same issue when looking at the main servers gui?
If not, I think you should file a support case on this. Might be some issues that affects more things.
Ive had this same issue in the past waiting (~24 hrs) for a new custom property to propagate to all nodes.
Were now running "2025.2.1". After recently creating a new custom property, it took less than 5 min.
do you mean we need to rollback to older version?
no additional web server
You probably should file a case with support then. It sh
That's not an option you will need to move to the latest versions in the future atleast and lot of things are changing, we are moving away from traditional module based to observability platform now, try finding out the root cause of the problem, probably post upgrade when you moved to observability platform there could be some obsolete stuff on your db.
It's likely the SWIS cache. If you're doing this via the API (SWQL), the changes usually show up almost instantly, but the Web UI takes a while to 'catch up' because of the way the pages are indexed. If it’s taking longer than 30 minutes, it might be worth checking if your 'Message Queuing' service is backed up.
We had this issue on 2020.2.6. I've not done much with Custom Properties in the current version we're running but that doesn't mean the issue has gone. Support and the devs worked for months on it and all we could decide was it was to do with IIS caching. If you restart IIS do the property changes show up? My homelab is running 2025.2.1 and I've just changed a couple of custom properties and they updated within a few minutes, so I hope 2025.4 hasn't broken more than just Azure.