# Diagnose Slow, Frozen, or Unresponsive Muhasib Screens

### Diagnose Slow, Frozen, or Unresponsive Muhasib Screens

### Overview

This guide will help you distinguish active work from a failed/frozen operation and collect evidence without causing duplicate writes.

The operation completes, is proven failed, or is safely stopped with duplicate-prevention evidence.

### Who can do this

You need access to Normal workflow access; system/log/performance diagnostics require administration authority.

### Before you start

Record screen/action, start time, data/filter size, company, workstation, network/SQL status, background operations, CPU/memory/disk symptoms, and message.

<div id="bkmrk-%F0%9F%9A%A8-importantmake-sure" style="border-left: 4px solid #dc2626; background: #fef2f2; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Before saving, check that the correct company is open and that you have permission to complete this task.</div>### Where to find it

Remain on the affected screen; use authorized Windows, SQL, network, notification, and log diagnostics.

### Diagnose Slow, Frozen, or Unresponsive Muhasib Screens

#### Step 1: Stop repeated clicks and wait for observable progress within local

Stop repeated clicks and wait for observable progress within local policy.

#### Step 2: Check whether the window/process is responding and whether SQL/network/background activity

Check whether the window/process is responding and whether SQL/network/background activity continues.

#### Step 3: For reports, reduce scope only to diagnose, not to declare full success

#### Step 4: For writes, query inquiry/history from another safe session only if

For writes, query inquiry/history from another safe session only if authorized.

#### Step 5: Preserve logs/timestamps before ending the process

#### Step 6: Restart only after classifying the operation outcome

### Check your work

Application responsiveness returns and the requested write/report result is verified at its full intended scope.

<div id="bkmrk-%F0%9F%92%A1-tipcheck-the-saved" style="border-left: 4px solid #2563eb; background: #eff6ff; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">Take a moment to check your work before closing the window. This small check can save time later.</div>### If something goes wrong

- A spinning UI can accompany active database work; do not kill it blindly.
- Never treat a smaller diagnostic report as proof the full report completed.

### Related guides

- [Recover from an Interrupted Save, Finalize, or Conversion](https://docs.muhasiberp.com/link/586)
- [Collect Safe Diagnostic Evidence for Support](https://docs.muhasiberp.com/link/594)
- [Understand Back Office Background Operations](https://docs.muhasiberp.com/link/287)

### What to do next

<div id="bkmrk-%E2%9C%85-next-actioncontinu" style="border-left: 4px solid #16a34a; background: #f0fdf4; padding: 12px 16px; margin: 15px 0; border-radius: 4px;">[**Recover from an Interrupted Save, Finalize, or Conversion**](https://docs.muhasiberp.com/link/586).</div>