Skip to Main Content
Spotfire Ideas Portal
Status Future Consideration
Product Spotfire
Categories Scheduled Updates
Created by Guest
Created on Jun 25, 2020

Timeout Setting for Long Running Reports

In Spotfire enviornments, intermittenly different reports keep loading for many hours and never completes execution. However, they are expected to complete in few mins. This issue is not analysis specific as it could happen with any report.

There could be multiple contributers for this issue like network performance, communication issues with different components like Spotfire server, node manager, application database etc. As per current process, Spotfire administrator has to keep monitor enviornment and close long running/hung/pending reports from Monitoring & Diagnostics tabs.

When many such reports keep loading for hours in a particular instance, that node manager instance goes into stress state then Spotfire administrator either has to keep monitor enviornment and close long running/hung/pending reports from Monitoring & Diagnostics tabs or restart services for the particular instance.

Idle/Inactive/session timeout doesnt help here as such report status is in progress/loading. It would be good if there can be a timeout setting for long running/pending/hung reports as well, so even if report is in loading state it can be close automatically (via timeout setting).

  • Attach files
  • Guest
    Aug 24, 2020

    Hi Miguel,

    Thanks for checking. This issue occurs is not restricted to only scheduled update or automation service job report, it can occur to any report. We can daily see this issue, and intermittently it leads to environment performance issue. Let me know if any questions.

  • Admin
    Miguel Díez
    Aug 24, 2020

    Hi Tejal,

    Does this happen for Scheduled Updates, Automated Services or both ?

    Does this happen often ? In other environments as well ?



Spotfire Scheduled Updates should cancel the job if run past "x" hours

we have some dashboards which are scheduled to refresh and some times it takes longer that it should and causing some spikes in CPU and memory on the data sources. So, if we can have the feature to configure something like if the SU runs for more ...
almost 4 years ago in Spotfire / Scheduled Updates 0 Future Consideration

Solution of Time out of rule that has been running for long and never complete

We have rule in schedule updates. This rule generally takes 2-3 hours to complete. But here rule is taking long time sometimes goes to 24 hrs and more and show status = running. So is there way that this refresh gets cancelled after certain time. ...
about 5 years ago in Spotfire / Scheduled Updates 2 Future Consideration

Dissociated time passed in waiting pool (running on the node) and time passed in loading (running on the node).

Sometime the analyse is running but it's waiting a free pool ... after the schedule loaded , we lost the time passed in waiting(when the status is running)... In summary of job, i would have more details:time passed in running (waiting) + time pas...
over 2 years ago in Spotfire / Scheduled Updates 0 Future Consideration