Skip to content

Go-Live Runbook

Your integration works end to end in sandbox and FSRI has issued your production credentials. This is the coordinated path to live traffic.

Production uses the same endpoint paths as sandbox. The base URL, token URL and content host change; see Environments.

Before Launch Week

  • Production credentials stored in your production secret store; environment configs fully separated from sandbox.
  • Production base URL, token URL and content host configured, including the event.origin check for the content player (see Workflows).
  • Launch window agreed with your FSRI integration contact.
  • Expected volumes shared: learner count at launch, catalog sync cadence, anticipated peak.
  • Your monitoring live: per-call status/latency logging, alerts on sustained 401/403/5xx.
  • Rollback plan on your side: ability to disable the FSA integration without breaking the rest of your LMS.

Launch Day

  1. Production smoke test (before opening to users): /ping → authenticated GET /courses → register one pilot user → play one module end-to-end.
  2. Enable for a pilot cohort first if your rollout model allows.
  3. FSRI monitors gateway metrics during the agreed window; you monitor your side.
  4. Confirm with your contact once traffic looks nominal.

First Two Weeks

  • Watch for 429s as real usage patterns emerge — sync schedules that worked in sandbox sometimes bunch up under production load.
  • Report anomalies in the learning record (missing completions, unexpected progress states) promptly — early data-quality catches are much cheaper.
  • Keep sandbox integration working — it's your test bed for every future change.

Incident During/After Launch

Use the escalation path. For a launch-window incident, contact the incident contact directly — don't wait on a ticket.