Repeated crashes are a symptom, not a diagnosis. The cause might involve application code, memory use, database connections, a particular record or an external service. Capturing a repeatable example is more useful than repeatedly restarting the application.
Collect evidence around the failure
Record the task, time, affected user and any error message. Note whether the problem started after an update or happens only with a certain file or record. Developers can compare these observations with logs in an authorised investigation.
Practical checks
- Keep examples of affected records without exposing unnecessary personal data.
- Check whether one device or all users are affected.
- Record what staff did immediately before the crash.
- Avoid repeated live experiments that could create duplicate transactions.
Questions and answers
Will reinstalling the application solve it?
It may help with some local installation problems, but it will not repair every database, server or code fault. Establish the cause before treating reinstallation as a solution.
Can the repair be tested safely?
Where practical, reproduce the fault in a test environment. Confirm the fix and check related tasks before returning the change to live use.
Discuss your existing software
Digital Solutions can review the available system and discuss an appropriate next step. Feasibility, access requirements and the scope of any chargeable investigation are agreed before work proceeds.
Explore our software support, project rescue and modernisation services.
Book a free 15-minute software review or contact Digital Solutions.