Why is my session taking so long to save?

If Insight is taking longer than several minutes to save a session, there may be something wrong. If you can, use the DUG Launcher to send logs and we will investigate and try to understand why.

There are common reasons Insight can take a long time to save a session:

Slow network or busy file server

Insight relies on the speed of the network and file server. If the file server or network is very busy, it can result in poor Insight performance.

How to identify:

  • Many users are affected.
  • All projects are affected.
  • Other software is affected.
  • Talk to other network users. Are they also running slowly?
  • Many actions (saving session, creating new items) take longer than expected).

Solutions:

  • Send logs.
  • Be patient. Wait longer.
  • Talk to the system administrator to identify performance problems.

It is waiting for another copy of Insight in the same project to complete some work

It is rare but sometimes another Insight in the same project will take a long time to complete its work. If this happens when it is writing to the database, your copy of Insight must wait for its turn to write the session. This should not take more than a few minutes.

More common when using busy projects with many active users.

How to identify:

  • Only one project is affected
  • Other users in the same project are affected.
  • Talk to other users in the project. Are they having similar problems? Are they also running slowly?
  • Many actions (saving session, creating new items) will take longer than expected.

Solutions:

  • Send logs.
  • Be patient. Wait longer.
  • Investigate whether the network or the file server is busy.

The connection to the server was lost

Temporary network errors can cause Windows to lose the connection to the project area. Usually it recovers quickly and is not noticeable. If the error happens when Insight is working, Insight may be unable to use the database without restarting.

Consider this if there are few users of a network project.

How to identify:

  • Only one project is affected
  • Only one user (or very few) are affected.
  • Talk to other users in the project. Are they also running slowly?
  • Any actions such as saving sessions, and creating new items will be stuck.

Solutions:

  • Send logs.
  • Talk to other users in the project. Are they having similar problems?
  • Manually close or kill Insight.

If the save takes more than 10 minutes and is not progressing, consider manually closing the Insight process. Insight performs an autosave of a session every 5 minutes (details here), so it is very rare to lose work.