Weird issue with query module. query.runSuiteQL is working fine while query.runSuiteQLPaged throws Unexpected Error. Has anyone experienced the same? any thoughts?

Yes, there are certain fields that behave differently depending on the method used. For example: Transaction Status returns different values depending on the method. There are also queries that return incorrect values when paginated. For example, when you use CONNECT_BY to traverse through a full bill of materials. The pagination does is not able to maintain the connection for these type of "recursive" or "traversing" queries

Makes sense. My query is complicated. Probably that's why.