Troubleshooting
This section explains common problems and how to resolve them.
If you are a staff user, contact your organization admin for access issues. Members should contact their library. Organization admins can search the CodeAchi support knowledge base first, then create a private ticket if the public guidance does not solve the issue.
Support pages keep public knowledge base articles and public tickets in the selected language. If you choose Bengali or Arabic, Support search and browsing show records written for that language instead of mixing unrelated English content.
A Page Does Not Open
If a page cannot be displayed, Libcodesk keeps the main work area available and shows Try again and Reload application instead of leaving a blank page. Choose Try again first. If the same page still fails, reload the application once and repeat the action. Staff should then report the page name, selected library, time, and action to their organization admin without sharing private member or account data.
Do And Don'ts
- Read the exact error message before changing data.
- Turn on diagnostic logging when reproducing Standalone app issues.
- Note the workflow, user, time, and setup mode when reporting a problem.
- Don't delete records or reset data before checking the cause.
- Don't share passwords, OTPs, tokens, or private files in support messages.
- Don't assume Cloud and Local errors have the same cause.
FAQ
Who should read this page?
Admins and staff should read this page when they need to understand or complete the Troubleshooting workflow in Libcodesk.
Does this work in both Libcodesk WebApp and Standalone app?
When a workflow differs between Libcodesk WebApp and the Standalone app, the guide points out the setup-specific step so staff can follow the right path.
Does local setup use the same steps?
Local setup follows the same user workflow where the feature exists, but the work stays on the Standalone app device instead of Cloud setup.
What permission do I need?
If you cannot see the menu or action, your staff role probably does not include the required permission. Ask your organization admin to review your role.
Why is the Save button disabled?
Save and update buttons stay disabled until Libcodesk detects a real change. This prevents accidental writes, unnecessary logs, and duplicate requests.
How do I fix validation errors?
Read the message beside the active button or inside the modal. Required fields, duplicate values, invalid dates, and permission issues must be corrected before saving.
Can I use imports instead of manual entry?
Where import is available, it is recommended for larger datasets. Always validate the file first and review row-level errors before importing.
Where should staff or members ask for help?
Staff should contact their organization admin. Members should contact their library. Organization admins may search the CodeAchi support knowledge base in the selected language and create a private ticket for license, billing, cloud access, or account ownership issues.