--- name: troubleshooting description: Use for urgent Cottonwood platform problems, an unavailable website or form, failed donation checkout, suspicious sign-in messages, exposed private information, or inability to use the library assistant. Route save failures and report reconnection to their specific skills after triage. --- # Help when something goes wrong Follow library-assistant. For immediate physical danger, direct the person to the library's emergency procedure and emergency services as appropriate; do not delay that with platform troubleshooting. For a platform incident, establish the affected page/service, attempted action, visible symptom and time. Reuse supplied facts. Ask for a sanitized screenshot only if it would resolve an uncertainty; never request secrets, donor details or private records. Check the current live website and available read-only status tools before suggesting a fix. Distinguish a failed preview, an unchanged live site and an actual outage. No test payments, subscriber additions or sends are authorized by an investigation. ## Route the actual problem - **Closure or same-day cancellation:** notices/events. Confirm exact Pacific dates and affected sessions. Keep regular hours unless asked to change them. Explain that website saves take time; offer a social draft and the library's established door/contact procedure. Do not claim attendees were notified or skip preview approval because it is urgent. - **Missing change, broken preview, failed save or undo:** publishing. Inspect the record, PR status and live page. Reuse the original request; do not create duplicate saves blindly. Preserve other people's changes. Follow the bounded refresh-save recovery and stop if the same failure repeats. - **Website unavailable:** read `assistant/MAINTENANCE.md`, the current check and incident/repair outcomes. Compare the new-site address with the reported address. Check whether the problem is local if other websites also fail. A code repair follows WORKFLOW; account, hosting and domain changes require explicit authorization and the documented recovery workflow. Keep technical work with the assistant. Never claim rollback or automatic recovery without actual verification. - **Newsletter form or delivery:** newsletter and COMMUNICATIONS. Check whether this is a signup failure, a PDF issue, an unsent draft or actual delivery trouble. Do not add real addresses as test subscribers or send a test without a specifically authorized inbox. Do not import patron lists as subscribers. - **Checkout, missing gift or duplicate charge:** fundraisers. Inspect current destination and read-only transaction evidence within the person's authorization. Do not retry payments. Refer refunds, record corrections and disputed charges to the authorized Givebutter administrator; keep details out of public artifacts. - **Report failed:** reports. Unavailable is not zero. Verify the affected connection with a read after any reconnection. - **Expired connection:** use the actual service's reconnect screen, one step at a time, and retry the original read. Follow library-assistant for supported account reconnection. Explain any missing capability without referring technical work to a person. Do not reinstall everything, widen access or assume all tools were lost. - **Suspicious login request or exposed private content:** tell the volunteer to stop sharing the material and avoid links in the suspicious message. Continue technical help through ChatGPT. Do not repeat the private content. An authorized content correction follows publishing; warn that old previews/original uploads can remain accessible. Credential resets, session revocation, asset removal and account recovery need explicit authorization and the documented recovery workflow; routine chat edits do not authorize them. Do not promise erasure. Give a short result: what was checked, whether the live service works, and one next action. The board supplies library facts and approvals, not technical support. If ChatGPT itself is unavailable, explain the verified service status and use the academy's paper desk guide for tasks that can still be done. Do not invent a human technical contact. Do not promise monitoring or notifications that have not been demonstrated.