Indicator with sys ID XYZ not found
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-26-2016 10:42 PM
hello everyone ,
the story so far: cloned prod over dev, and upgraded to helsinki patch 4
PA jobs ran successfully apart from this error in Incident: "Indicator with sys ID XYZ not found"
I am struggling to locate what is making a call to something that doesn't exist! Any clues please?
- Labels:
-
Performance Analytics
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2016 12:59 AM
looks like I found the culprit, right under my nose:
In the Job, there are indicators - the top one is named "(empty)"
However , in Helsinki I am seeing 15 indicators and in Prod only 8 - so I am currently unsure whether the upgrade has added a load more indicators
The sys_id of the missing indicator is: 1e756e55eb7302001e68286b1206fe4f FYI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-03-2016 04:29 PM
This same thing happened to me. Also, it's showing the same exact sys_id in the error of the job log. I noticed the empty record in the indicators for the job too. After cloning prod over our pre-prod instance, new indicators didn't make it over. Maybe it has to do with that. For example, our pre-prod instance (which was just cloned), only has 34 indicators included in one of our jobs, while production has 42. I validated that some of the newer indicators created in Production didn't make it over during the clone. Maybe the same thing happened for you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-30-2017 07:49 AM
Yep, I've got it to with the same sys_id. I also have the empty one that mrswann listed above, but the sys_id does not match the empty one.