title: Using ScheduledActionService.LaunchForTest a bad idea?
body: <p>In my app there are settings for changing how the live tile should look like (color, background and so on). Problem is that if the user changes this it takes about 30 minutes before the live tile is updated with the new settings since all the code (quite a lot of code) is beeing executed in my OnInvoke function.</p>
  
  <p>Is it a bad idea to call ScheduledActionService.LaunchForTest everytime the user changes the live tile settings in my app?</p>
  
  <pre><code>ScheduledActionService.LaunchForTest("PA77RT", TimeSpan.FromMilliseconds(2000));
  </code></pre>
  
  <p>I know that it might be considered "not perfect" doing like this but my question is if this will have any other downsides that I don't know of?</p>
  
  <p>Thanks in advance.</p>