500 Internal Server Error while running a sub flow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-30-2025 01:02 PM
Hello,
I have created a data stream to fetch data from an API, and it was working fine. However, after adding this data stream to a subflow, where I am trying to create a record in a table for each data entry, it worked for a few records. But after processing some records, I started encountering an internal server error. Could you help me figure out what might be causing this issue?
Thank you in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-30-2025 10:41 PM
A 500 error only indicates that 'something' is wrong, not what is wrong. Do you have any other information related to the error? Can you share your setup as well, so we can see what it is that you are trying to do?
Please mark any helpful or correct solutions as such. That helps others find their solutions.
Mark
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-30-2025 10:47 PM
Hi,
Internal server most of the time because it stops responding because of unknown reason, you can try after some time it might work.
If it doesn't work then there could be multiple issue causing like Resource execution limits, Faulty or incomplete data, doesn't handle errors gracefully, if required ip/op are missing from your action, API integrations limits.
Troubleshoot & Fix:
Review the logs, check for table, memory errors, Try to add the logging step in data stream, always consider adding Try/Catch blocks to log the error message.
Thanks,
Bhimashankar H
-------------------------------------------------------------------------------------------------
If my response points you in the right directions, please consider marking it as 'Helpful' & 'Correct'. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-30-2025 11:02 PM
I recommend checking the logs to identify which record caused the failure and reviewing the data for any inconsistencies. Also, ensure error handling is in place to skip or log problematic records without stopping the whole flow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-31-2025 09:12 AM
Thank you all.
It is because the pagination step was not configured correctly. So, it was looping over and over again.