Press CTRL+K to open search

Operations

  • Published on Aug 26, 2026
  • 1 minute(s) read
  • G
 Prev Next

Feedback Manager Operations

Operational diagnostics and recovery guidance for Feedback Manager.

Quick Health Checks

  1. Confirm FEEDBACK_PROVIDER is set to a supported value.
  2. Confirm provider-specific env vars are present for the selected provider.
  3. Confirm auth cookies are present on incoming request.
  4. Confirm provider destination is reachable and permissioned.

Failure Modes

Surface Condition Response
API route Missing auth user cookie 401 Unauthorized
API route Missing site cookies 400 Missing site information
Factory Unsupported or missing provider config.missing error
Provider init Missing provider env vars config.missing error
Provider write External write failure success false with error
Route catch Unexpected exception 500 Failed to submit feedback

Runbook

1) Unauthorized or bad request responses

Symptoms:

  • 401 Unauthorized
  • 400 Missing site information in cookies

Checks:

  • Verify auth middleware and cookie forwarding
  • Verify id, siteId, and site cookies on request

Fix:

  • Restore auth/session propagation
  • Ensure request is sent with credentials include from client

Verify:

  • Submit feedback from authenticated session and confirm non-401/non-400 outcome

2) Provider configuration failures

Symptoms:

  • config.missing at provider creation
  • 500 responses on submit

Checks:

  • Verify FEEDBACK_PROVIDER
  • Verify provider-owned env vars for selected provider

Fix:

  • Correct selector and provider env vars
  • Restart process if environment injection requires restart

Verify:

  • Successful provider initialization and successful submission

3) Provider destination failures

Symptoms:

  • Provider returns success false with destination error message

Checks:

  • Destination credentials and permissions
  • Destination identifiers such as sheet ID and range

Fix:

  • Correct credentials and destination access
  • Re-run submission test

Verify:

  • Provider write returns success true

Retry Semantics

Current behavior:

  • Provider factory clears rejected initialization promises and allows retry on next call.
  • Route does not perform write retry loops.

Non-goals in current implementation:

  • No built-in exponential backoff for provider write failures
  • No queue or deferred retry pipeline

Extensibility Operations Notes

When adding a provider:

  1. Add provider-specific operational checks to the provider doc file under providers/
  2. Keep global operations page focused on integration-wide behavior
  3. Keep provider troubleshooting isolated to provider implementation details