Javascript backend scripts - Query response hangs

Question

I am modifying a database Read script to filter based on data within a related table.
However, when this is executed from my iOS app, it hangs. A response is never sent back.
Here's what I have. What am I doing wrong?
function read(query, user, request) {
var helpers = require('../shared/helpers.js');
helpers.getUserEmailNew(user, function (email) {
//console.log("User '%j' maps to email address: %j", user, email);
// Return surveys for the currently authenticated user
// by the email address we just found.
var sql = 'select * from SurveyAnswer where SurveyId in ' +
'(select id from survey where username = ? and submitted = 0 and __deleted = 0)';
mssql.query(sql, [email], {
success: function(results) {
request.respond(statusCodes.OK, results);
error: function(err) {
console.log("Error retrieving SurveyAnswer records: " + err);
request.respond(500, err);
The referenced getUserEmailNew helper is not the issue as it is referenced in the same way just fine within other scripts.
If there is a better way to include related tables within a query, I'm all ears!
Thanks :)

Answer 1

In digging deeper into this issue, I wanted to prove that the above script was indeed successfully executing. To do this, I added a log entry within the
success callback of my mssql query:
console.log("Retrieved %j SurveyAnswers for %j", results.length, email);
When I observe the logs while my client is requesting this table data, I see entry after entry (essentially running for all eternity before forcing the app to close) the above text. Essentially, it says something like "Retrieved 257 SurveyAnswers for
[email protected]".
Now, as a point of clarification, I am utilizing offline synchronization via the 1.3.2 version of the WindowsAzure.MobileServices component within a Xamarin iOS app. I have no issues with any other table that I am synchronizing data from, but this is the
only table where I'm running a dynamic mssql query instead of simply response.execute().
My first inclination after looking at the logs was that the offline sync process automatically implements data paging. Surely this must mean that not running the response.execute() method is breaking its attempt at paging. To test this theory, I limited
the result set to 10 rows. No dice. Still endless calls by virtue of the above log entries.
For completion's sake, here's my sync call to this particular Read script on the SurveyAnswer table from my mobile app (was working before I switched over to the mssql call):
await this.table.PullAsync(uniqueId, table.CreateQuery());
Again, this same call works for all other tables just fine, as well as this table while I was still implementing a simple response.execute() within my read script on the server.
What am I missing here? This is driving me nuts! Is there a better way to include other tables within my select query than how I'm doing it above? I figure it is possible to run a response.execute() and then in the success callback, make a separate call
to the other table and then loop through my results, removing any that don't apply, but this seems like it would be wildly inefficient, especially if I'm dumping thousands of records.
Thoughts? Suggestions? Please?