Unable to insert record in group member table through flow designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-13-2022 04:16 AM
I have a flow designer developed for AD integration with Servicenow through AD spoke
While trying to add user to group in Servicenow instance after adding the users to the AD group I am getting an error that says "Error occurred while inserting record : null"
I have referred to the KB article available but they do not provide a clear fix as expected
I have already referred to these KBs: https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0827213
And related KBs to this error but unable to find a fix
Below is the flow with error execution:
Actual flow logic:
Please let me know if you could find the issue?
- Labels:
-
flow designer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2025 08:40 AM
Hello @User332204 , @Toshu , @Radek , @Ankur Bawiskar
We have same issue, since last 3 years flow has been working, Suddenly from last weeks it stopped working and I'm receiving the same error as you. Can you please confirm how you have fixed this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-18-2025 09:40 AM
can you post a new question and share all the details, screenshots and tag me there as this is an old thread?
Ankur
✨ Certified Technical Architect || ✨ 9x ServiceNow MVP || ✨ ServiceNow Community Leader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-19-2025 12:46 AM
As far as I remember, we are still facing this issue - this is caused by ServiceNow design. When attempting to add a user to the HR group, the system requires the HR Admin role to create the record. Since the flow runs under the system context and does not include the HR Admin role by default, it fails, resulting in a null error. ServiceNow does not recommend assigning the HR Admin role to the Admin role.
As a workaround, we implemented a scheduled script where we pass all necessary variables, and in the scheduled script, we set it to run as HR Admin. While this solution isn't ideal, it is working.
The error appears only for applications which have similar setup like HR - you have a separate admin role for access and the role is not included in system administrator (OOB) user record.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-22-2025 02:33 AM
Hello @Radek , Could you please provide me the schedule code and condition how you have implemented ?
Kind Regards,
Atanu Maity
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-10-2025 11:25 AM
Sorry I’ve missed your message - do you still want some screenshots etc?