Flow Designer Internal Server Error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2024 09:49 AM - edited 01-02-2024 10:19 AM
Hello Everyone,
I am working on an integration via the flow designer, and unfortunately one of my action steps results in an "Internal Server Error" every time I run it.
When I go to the execution, it shows that the flow was cancelled.
My question is, how can I get more information on what is causing the error? The flow takes a very long time as it is pulling some ~7,000 records from another system so I suspect it might be time or memory related, but if anyone has any info on how to better debug this error, it would be greatly appreciated.
Thanks,
Andrew
Edit: The table I am pushing this data to is a custom table which does not have any SLA's or Business Rules that would be causing this error. On each run, a little under 4,000 of these records make it in to the table before it errors out, however the number is not consistent so I also don't believe it is the result of a bad record being pushed to the table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2024 09:56 AM
Hi @Andrew158
May be you get some clue
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2024 10:16 AM
Hey, thanks for replying. I should probably add some more information to the original post here, but the table I am integrating this data into is custom, so I know the error is not the result of any SLA's or business rules on the table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2024 10:27 AM
Then mate, it all about the data and how that data is coming and store in SN.
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-02-2024 11:42 AM
I have found that this only occurs when I test the flow action in the foreground, and that when I run it in the background I do not get the error and all of the records populate. For my purposes this is fine, however I am still curious as to what makes this fail when run in the foreground if anyone has any info on that.