Troubleshooting for Agency resource scheduling dashboard
This agency resource scheduling dashboard troubleshooting page covers agency resource scheduling dashboard. First, choose one small task you can check by hand. Then follow the steps below and compare the result with your source information.
The download is a runnable portal + offline workspace. This page explains one part of its use. For the full process, follow the ten linked guides in order or open the section you need. Keep your source notes with your working files.
If the package does not open
For agency resource scheduling dashboard, confirm that the ZIP is fully downloaded and extracted. Open the supplied entry file from the extracted folder. Keep dependencies together and read START-HERE.txt.
If the separate customer application fails to start, follow RUN-PORTAL.txt, check the required Python version and read the error in the server console. Opening product.html does not start that server.
If an output is missing or unexpected
The product exposes these inputs: Customer; Service; Staff or resource; Start; End; Status; Contact; Notes.
The delivered interface includes these labels and controls: Download JSON backup; Restore backup; Print / PDF; Load example; Clear workspace; Close; Save record.
- Repeat the task with a small fictional case and record the expected result.
- Review required inputs, date formats, numbers and selected records.
- Confirm whether the capability is actually listed in the package scope.
- Inspect the exported file rather than relying only on a preview.
- Restore a backup only in a separate practice copy until you understand the problem.
If you need help
Includes an offline workspace plus a runnable Python server application. Python 3.11+, hosting and HTTPS setup are required for public access; hosting and automatic email/payment collection are not included. Includes a runnable Python customer application; public hosting is configured by the buyer.
Contact the store with the product number, the step that failed, your browser or runtime version, and the exact error. Use fictional reproductions and avoid sending passwords, payment details or customer records.
Narrow the problem one step at a time
First, write down the exact action that fails. Note the error message and what you expected instead. Next, repeat the action in a clean practice copy with fictional inputs.
If the clean copy works, compare it with your working version. Check recent edits and missing files. However, keep the original working copy intact while you investigate. Finally, share a small reproduction with support if you still need help. Do not send private customer data.
Details to check in this product
- Customer: confirm the source and keep a clear reference.
- Service: check the value against your practice case.
- Staff or resource: review the result before you save or share it.
- Start: confirm the source and keep a clear reference.
- End: check the value against your practice case.
- Status: review the result before you save or share it.
- Contact: confirm the source and keep a clear reference.
- Notes: check the value against your practice case.
A useful reference
Use an isolated environment when following the runnable application setup. Read the Python documentation on virtual environments for more detail.