- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:14 AM
I've encountered something very odd today. A UI policy that continues running after being deleted.
I had a UI policy that was setting some incident fields to read only on specific state values. This was inactive - but it turned out that it was still running. I searched for UI policies running against task doing the same thing - but there are none. UI policy debugging shows that it is the UI policy named "Set fields to read only on resolve". There was only one of these. And this UI policy was certainly inactive.
As the UI policy was inactive and had been replaced with another, I decided to delete it just to stop this odd behaviour.
And what do you know? It's still running and still showing up in the debug log. Even after clearing the log, creating a new incident, and trying again, it's still there. Clearing the log, disable debug, re-enable debug - retry. Still happening. cache.do - retry. Still happening!
Has anyone seen anything similar? This is a Fuji P12 HF1 version instance.
I'm starting to worry that maybe I'm losing my marbles...
Cheers,
Danny
Solved! Go to Solution.
- Labels:
-
User Interface (UI)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:47 AM
Two options - option 1: turn on the field watcher on that field and see what's going on.
Field Watcher - ServiceNow Wiki
Option 2: check sys_ui_policy_action to ensure no other UI policies are working against that table/field.
Also, check your client scripts! (which may be revealed by option 1)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:27 AM
Hi Daniel,
Two things - did you clear the browser cache?
Did you clear the ServiceNow cache (https://yourinstance.service-now.com/cache.do)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:35 AM
Hi - yeah, tried that. No dice.
I've actually now discovered by looking at a clone of this instance that in fact the one I deleted is one that was very similarly named to the one that is running. But it is not the same one.
The one that is running doesn't exist anywhere in the UI Policy table. At all. I'm looking at this with a full admin account too. Elevated permissions, and I can't see it.
Ghosts in the machine!
Think I may just have to log an incident with SN..

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:47 AM
Two options - option 1: turn on the field watcher on that field and see what's going on.
Field Watcher - ServiceNow Wiki
Option 2: check sys_ui_policy_action to ensure no other UI policies are working against that table/field.
Also, check your client scripts! (which may be revealed by option 1)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-31-2016 09:50 AM
Hi Chuck,
Field watcher is what's showing me that it's running. States "17:39:49 (269)UI POLICY - "Set fields to read only on resolve" ReadOnly set to false" - so it looks like a UI policy.
May be that a client script can show as a UI policy though? Will give them a check - thanks!
D