Forum Discussion

barak's avatar
barak
Microsoft Employee
10 years ago

Schedule Data Refresh does not get scheduled

hi

we have dashboard that was last refreshed at  "Sat Jun 11 2016 22:19:12 GMT+03:00" and the next refresh should have been at "Mon Jun 13 2016 18:00:00 GMT+03:00" but this time as passed and the refresh did not happaned.

 

i tried to refresh manually but it seems it didnt have any effect. what can i do to resolve it?

 

thanks

barak

Need Help

4 Replies

  • curtisp's avatar
    curtisp
    Helper II
    10 years ago

    Some questions:

     

    * Pro or Free version?  - free version gives you 4 hour windows of time in which refresh can be scheduled, maybe it didn't happen exactly when you thought but did later in that window?

     

    * If you go to Dataset - Schedule Refresh - and look at refresh history, does it show refresh happened? If yes it possible dataset data source was not refreshed? eg refresh happened but no new data was available?

     

     

    * Is your Schedule Refresh set up like the screenshot? 

     

     

    * Does the refresh work if you do it manually?  It might be that the connection details have been changed or not saved properly?

    • barak's avatar
      barak
      Microsoft Employee
      10 years ago

      * I think our account is Pro (internal Microsoft use)

      * The refresh did not happaned since 11/06

       

       

       

       

       

       

       

       

       

       

       

       

       

       

       

      * We setup the schedule to run every 3 hours

      * it does not work manually but it seems all the credentials are fine:

       

       

       

       

       

       

       

       

       

       

       

       

       

      • curtisp's avatar
        curtisp
        Helper II
        10 years ago

        You have the Pro version. The Free version has limited scheduling features (like my screenshot). You are able to schedule exact times.

         

        Your Refresh History shows the failed job which has link to show details. If you look at that does it provide any info about the reasonn the connection is failing?

         

        If it isn't running manually with On Demand refresh either then you will need to resolve that in order to get job running.

         

        Something must have changed with Azure db connection, or on the local machine it is running from like firewall or port blocking, maybe a local SQL server db taking up port 1433?