Qliksense dashboard refresh does not happen for the 2nd time

[Jeyarajerp]

Hi,

Have setup a dashboard recently in Qliksense . In the data load editor , configured a simple query that connects to a sybase ASE database  and gets the data.

Now have setup an autosys job ( that runs twice a day) to refresh the data into Qliksense Dashboard. The first run of autosys job gets the actual data from dataserver and loads into Qliksense , so all good.

But when the job runs for the 2nd time , it does not really seem to get data from Dataserver. Rather just reloads the same data that was loaded during the 1st run(picks up from some sort of QS cache?).  I have confirmed this by comparing number of rows getting loaded vs the no. of rows in the DB.  Would greatly appreciate any inputs regarding this.

Thanks,

Jeyaraj

[NadiaB]

Hi @Jeyarajerp 

Have you compared the log from the first execution vs the one that correspond of the second execution?

[Jeyarajerp]

Hi Nadia,

I have compared this and number of rows being fetched in the 2nd time is
same as first time. Even though data base has diff number of rows during
2nd time. Is there a reload frequency on the dashboard which can restrict
the number of data loads in a day.

Regards,
Jeyaraj

[NadiaB · Accepted solution]

It shouldn't be a problem

Could you verify the app is pointing to the right data source and that the new data in the DB is available at the time the task is executed?

Kind regards.

[Jeyarajerp]

The data source is correct. In fact , for the first time in a given
day,data gets loaded properly. Only an issue with sub sequent loads.

Also checked the data in source during refresh and it has expected data.
Even I forced the refresh multiple times after confirming data in the
source. But it just loads same data from the refresh happened for first
time in the day.

Regards,
Jeyaraj

[Jeyarajerp]

For some reason , out data connection configured in qliksense was pointing to the DR server instead of main server.

There is a lag in replication to DR server from main , which was causing all of the refresh issue.

Thanks for the help.

Regards,

Jeyaraj