Troubleshooting
Plain-English troubleshooting for login, setup, email, queues, reports, screenshots, attendance, payroll, and static documentation.
Workflow
- Troubleshooting tableAdmin / Reviewer: Use this table when a user reports that something is not working.
| Stage | Actor | Action | Result |
|---|---|---|---|
| Troubleshooting table | Admin / Reviewer | Use this table when a user reports that something is not working. | The filtered list supports review, export, or action. |
Create the missing setup data first. Empty shifts, branches, departments, roles, or employees usually mean the foundation step was skipped.
Check SMTP settings, queue workers, provider credentials, spam folders, and storage/logs/laravel.log.
Check Settings > AI for enabled status, endpoint, model, encrypted API key, timeout, and max draft-node limits. Guided parsing remains available without AI.
Review the preview drawer messages. Positions need a department parent, manager scopes need a matching user, and invalid parent relationships are blocked before apply.
Regenerate screenshots after clearing password/token/API key fields. Stored SMTP, Twilio, and AI secrets should be masked or blank in forms and docs.
Confirm the scheduler and queue worker are running. Scheduled reports and queued notifications are not instant without workers.
Check shift time, timezone, holiday override, duplicate punches, correction queue, and manual remarks before payroll.
Open /documentation/assets/css/app.css directly. If it fails, the static docs rewrite rule or file path is wrong.
Troubleshooting table
Use this table when a user reports that something is not working.
| Column | What it means | Where it comes from | Example interpretation |
|---|---|---|---|
| Problem | What the user says. | support report. | I cannot see documentation. |
| Likely cause | Most common explanation. | routing/config/data. | Root rewrite sent /documentation into Laravel. |
| What to check | Fast verification. | browser/command/log. | Open /documentation/index.html and CSS asset. |
| Fix | Recommended correction. | code/config/ops. | Allow documentation rewrite before front controller. |
| Prevention | How to avoid repeat. | test/docs/process. | Regression test static docs routing. |
- Open or edit the record when permission allows it.
- Filter the list without losing the current page context.
- Use status badges to decide which item needs attention first.
Main docs show essential fields only. Open Documentation Coverage for every detected source field, action, column, route hint, controller hint, and test hint.