none
Deleted

Answers

  • Hi Lukas --

    We're looking into what causes this and hope to have a resolution in the near future. In the meantime, if you run into this, can you try one of these solutions:

    1. In the portal, select your mobile service, select the configure tab, change ENABLE DYNAMIC SCHEMA and save the change. Then you can put it back to the original setting and save it again.
    2. If you use the Azure CLI, issue the command: azure mobile restart <servicename>

    Ultimately we're trying to force a restart of your service so it picks up your changes. Both of these should accomplish that. Let me know if neither of these work and I can investigate further.


    Brett Samblanet -- Windows Azure Mobile Services

    Thursday, June 12, 2014 6:20 PM

All replies

  • Hi Lukas --

    We're looking into what causes this and hope to have a resolution in the near future. In the meantime, if you run into this, can you try one of these solutions:

    1. In the portal, select your mobile service, select the configure tab, change ENABLE DYNAMIC SCHEMA and save the change. Then you can put it back to the original setting and save it again.
    2. If you use the Azure CLI, issue the command: azure mobile restart <servicename>

    Ultimately we're trying to force a restart of your service so it picks up your changes. Both of these should accomplish that. Let me know if neither of these work and I can investigate further.


    Brett Samblanet -- Windows Azure Mobile Services

    Thursday, June 12, 2014 6:20 PM
  • Deleted
    Friday, June 13, 2014 12:43 PM
  • Hey Brett,

    Any update on this? The first step works for me, but I have to do it every time I update a scheduler script at the moment.

    Saturday, October 18, 2014 8:08 PM