**BUG REPORT — Language Reactor critical server-side failures**

Bug
1

:hammer_and_wrench:

cb101f30-9360-4419-aac3-980d93b3f12d
cb101f30-9360-4419-aac3-980d93b3f12d1907×130 11.9 KB

Title:
Critical server-side failure: NLP data, word highlighting, sentence saving, and flashcard sync broken across all platforms

Summary

Language Reactor currently experiences severe server-side instability.
Core features (NLP linguistic data, word highlighting, sentence saving, flashcard progress sync) fail consistently across browsers and devices.
Issue confirmed by multiple users and reproducible in clean environments.

Environment

Affected platforms:

  • Chrome (latest version)
  • Firefox (latest version)
  • Windows
  • Android app
  • Multiple user profiles
  • Clean browser profiles with no extensions

The issue is not device-specific or profile-specific.

Steps to Reproduce

  1. Open YouTube or Netflix with Language Reactor enabled.
  2. Attempt to click on any subtitle word.
  3. Attempt to save a sentence.
  4. Open Flashcards → rate a card.
  5. Attempt to load linguistic data (word definition, grammar, examples).

Actual Behavior

  • Word highlighting fails intermittently.
  • Morphological/linguistic data cannot be retrieved.
  • SYSTEM ERROR displayed:
Failed to retrieve linguistic data: NETWORK_ERROR Lang: xx

(Observed for German, English, Russian, Japanese, etc.)

  • Sentence saving returns server errors.
  • Flashcards fail to save or update progress:
Server error. Please try again later.
  • Errors appear even in:
    • clean Chrome/Firefox profiles
    • fresh installations
    • different Google accounts
    • different OS
    • mobile app

This strongly indicates backend / server-side failure, not client-side.

Expected Behavior

  • Stable retrieval of linguistic data from LR backend
  • Reliable word highlighting
  • Successful sentence saving
  • Flashcards syncing without server errors
  • Consistent behavior across browsers and devices

Additional Notes

  • The issue appears globally and is reported by multiple users over several days.
  • Temporary partial recovery occurs (features work for a few seconds), then fail again → consistent with server restarts or unstable backend cluster.
  • This affects both free and paid users; the service is currently largely non-functional.

Request

Please provide:

  1. Acknowledgment of the ongoing server-side issue
  2. Status update on backend recovery
  3. Approximate ETA for full restoration of functionality
  4. Any temporary workarounds, if available

Attachments

Screenshots of errors (you may attach твой скрин):

  • NETWORK_ERROR Lang: xx
  • Flashcard “Server error”
  • Failed sentence saving
1 Like