
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-30-2021 09:55 AM
I have 40 different Service Maps that have been working with no issues. Now this morning 14 of them have the following error:
Error on server request getServiceTimeline. Can't find ServiceLayer 'af185b881b1d7c1064c8a686624bcbce' (the Sys ID varies depending on the Application Service).
Any ideas how I resolve this issue? All of these maps are working fine in my Pre-Prod instances. But for some reason in Production I am seeing this on maps that were fine for a couple of months.
I have already tried on one of them to delete the entry points and add them back again. But every time I do this and click on View Map these error still comes up.
Solved! Go to Solution.
- Labels:
-
Service Mapping

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2021 08:48 AM
Apparently in my case this is known Problem. HI Support ran a script that the resolved the issue on my maps. They will be releasing a fix in the future to avoid this happening.
The sad part is the fix caused me to lose all history on those impacts maps.
There is some scheduled job that apparently deleted the information for these maps. Not sure what triggered the cleanup job to do that, but have HI support looking into it to provide the root cause as to why these maps experienced this issue.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-31-2021 12:55 AM
Hello,
I think this community article may be helpful to you

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2021 08:48 AM
Apparently in my case this is known Problem. HI Support ran a script that the resolved the issue on my maps. They will be releasing a fix in the future to avoid this happening.
The sad part is the fix caused me to lose all history on those impacts maps.
There is some scheduled job that apparently deleted the information for these maps. Not sure what triggered the cleanup job to do that, but have HI support looking into it to provide the root cause as to why these maps experienced this issue.