Flow Error: Invalid target record for notification
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-31-2021 01:16 PM
Hello,
I have recently taken over the task of trying to administrate service now. The last person created a flow that appears to error every time with "Invalid target record for notification" on the Notification: Hardware Delivert Incoming action. Due to this error an SCTASK is never created. What is interesting is if I open the Flow, click Test and enter the RIT the test completes and it pushes through the SCTASK with no error.
I am new to the platform so if you could please be detailed with steps required for any suggestions you might have.
Thanks very much!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-01-2021 02:03 PM
I would like to think so. There was nothing 'fundamentally' wrong with anything else. Glad it works now!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-01-2021 02:07 PM
Thanks very much for your assistance! Can I ask what made you think to update the action description? Thanks again!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-02-2021 06:28 AM
You're very welcome! It was more a process of elimination. The error clearly referenced an issue with the Notification step, but we validated that the inputs were correct. Which means the "hand-off" was failing.
By updating a non-consequential field (e.g. the description) the record gets processed again, and the apparent glitch/corruption disappears. It might have been related to a bad fix after an incomplete move from a different system.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-15-2021 03:07 PM
Well thanks again for your help but it looks like the problem is still occurring. Seemed to work fine with those couple tests, now another user submitted a request and same notification errors occur....My test submissions that were working are now displaying the same error. I went ahead and updated the description again and now my test went through. So it would appear the fix works but only temporarily....any suggestions?
Edit: It would appear that editing the action description works for one request then goes back to erroring on notification in subsequent requests.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-16-2021 07:00 AM
My suspicion would be that something is touching the action and impacting the flow as a whole.
This might need ServiceNow support attention, with log reviews and stack debugging.