Team Administration: Save and recovery
Operational reference for save and recovery in Team Administration.
Save and recovery
No automatic publication occurs. Every mutation requires a selected, authorized team, explicit Save/confirmation, optimistic team/record versions, and valid season context where relevant. Stable creation IDs protect against duplicate requests. A timeout/conflict retains the form: reload/review the latest Hub record before retrying. Reload/new/context changes ask before discarding unsaved forms. Local forms are in memory; export any needed notes before leaving. There is no offline write queue or automatic retry.
Snapshots are bounded to 250 roster entries/practices, 500 events and 50 recent posts; date filters cover at most a year. Practice notes and post bodies load only when opened. Team/opponent/venue searches are bounded. Private data is under ~/.ga360-team-admin, installed code under ~/.local/share/gameaction360-team-admin; updates/uninstall retain data and runtime dependencies. This first independent release has no previous ZIP; future releases retain current and immediately preceding ZIPs only.
Python local-session/entitlement/HTTP/installer checks and JavaScript UI tests are included. Rails integration/security tests are supplied but could not run here without Ruby/Rails. Native Mac/Linux browser, kiosk, touch and full Hub behavior require staging verification. No deployment has been performed.
Need more help with this?
Search a specific symptom, review related guides below, or prepare a report with the app version, operating system and exact error. Guides describe the documented release; installed versions and subscription access can differ.
Prepare a support report