title: Meteor.call in client doesn't wait when the called method has another call inside
body: <p>I am following what I've read around being the standard way to use Meteor.call but it's behaving strangely in this scenario:</p>
  
  <p>Client:</p>
  
  <pre><code>Template.sometemplate.events({
      'submit .somebutton'(event){
           ...
           Meteor.call('stuff.someMethod', param1, function (err, res){
                console.log(err);
                console.log(res);
           };
      }
  })
  </code></pre>
  
  <p>Server /api/stuff.js:</p>
  
  <pre><code>Meteor.methods({
      'stuff.someMethod'(param1){
           ...
           Meteor.call('otherstuff.someOtherMethod', param1, function(err, res){
                    if(err){ throw new Meteor.Error(400,'wrong things');}
                    if(res) { return 'ok';}
               }
           );
      }
  })
  </code></pre>
  
  <p>Server /api/otherstuff.js:</p>
  
  <pre><code>Meteor.methods({
      'otherstuff.someOtherMethod'(param1){
           ...
           return OtherStuff.findOne(query);
      }
  })
  </code></pre>
  
  <p>On the client side I click and immediately see the console.log for both err and res as undefined. Whereas in other parts of the application when the client calls a server method, which is not calling another method, the client waits for the answer before executing the asynch callback.</p>
  
  <p>There must be something wrong in how I use the Meteor.call inside a server method calling another server method. The scenario is that for instance I want to insert a document and while doing so I want to check some values in order to link it to other documents from other collections. </p>
  
  <p>Thank you very much,
  T.</p>