Skip to documentation
FFranchiseOSDOCUMENTATION

Troubleshooting / Everyone

Collect useful information for support

Give staff or the operator enough context to find the failing workflow.

Include the right details

Provide the league name, team(s), actual calendar time and timezone, command or screen, the exact error, and what you expected to happen. For a matchup, include season/week and home/away teams. For a trade, ticket, reward or media job, include its visible identifier or link.

  1. Check whether the action actually saved by reopening its view or wallet ledger.
  2. Note the latest relevant sync status and warnings if data is involved.
  3. Include a screenshot with the selected matchup/team and error visible.
  4. State the last successful step and whether another user sees the same problem.

Keep credentials private

Do not include EA passwords, OAuth tokens, database URLs, dashboard secrets or private import URLs in a support screenshot or public channel. Public player names and matchup details are usually enough to begin; the operator can inspect scoped records through authorized tooling.

FranchiseOS documentation · League features and permissions vary. If behavior differs, include the screen, command and league when reporting it.

Search documentation

40+ results · Arrow keys to choose, Enter to open