Multiple Surveys generated
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎02-08-2017 08:33 PM
Hi All,
We have surveys that gets generated once HR case state is changes to Closed complete. However, I could see two surveys being generated.
Couldn't find any issue with the Trigger conditions.
I have checked activity on the HR case, and could see 'Close Complete' state being generated twice. I think this is what has triggered two surveys, but unable to find the reason behind multiple activity for the same state. I have checked other cases as well, but this doesn't happens for all, but only for few cases.
Regards,
Manjyot
- Labels:
-
HR Service Delivery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-24-2017 08:06 AM
Hey Guys
I have the same issue with duplicate survey for Incidents. Our survey is triggering twice one with blank page ( without any details in it ) and one is the proper survey page. Weird thing this is happening only in prod but not in sub prod instances which is hard to find out or replicate. We recently cloned our Dev and Test instance from prod but the issue is not replicated in either of the instances. We have only script include Incident closed survey for this and one business rule which triggers notifications for all surveys in our instance. I'm not sure where is the issue and what to find as this is only happening in prod. I have compared my scrips and rules of prod instance with our sub prod instances but everything seems to be same no code difference nothing etc. In one of the above thread i read to find the trigger iD by navigating to assessment table. But when i did that, i don't see any record in recent days and the latest record i see 'Due Date' was in 2015 and trigger id column in empty for all these records.
Just wondering if any one found the solution for this thread?
Regards!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2021 01:39 PM
I noticed this issue after an upgrade to Rome.
Please, refer to this article: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0830680.
One way to fix it is to "edit your Trigger Conditions so the repeat interval is set to something greater than 1 second."