app  /  playbooks  /  Polestar 2 — propulsion loss
high severity propulsion loss 2021—2024 dealer

Polestar 2 propulsion loss (2021—2024)

Polestar 2 · 2021—2024 · all trims

Reported symptoms

  • Vehicle displays propulsion, drive system, or high-voltage warning message
  • Vehicle enters reduced-power mode, limp mode, or stop-safely condition
  • Acceleration is limited unexpectedly or power delivery cuts out intermittently
  • Charging or high-voltage warning appears before or after propulsion symptoms
  • Polestar app reports vehicle errors or inconsistent status
  • Service center references inverter, BMS (Battery Management System), high-voltage, drive-unit, or software diagnostics

Questions to ask

Pose these to the service advisor at intake. Request answers in writing or via email.
  1. Were stored, pending, or historical propulsion, inverter, BMS, drive-unit, or high-voltage codes found?
  2. What software version was installed before and after service?
  3. Was the issue reproduced during a road test or diagnostic procedure?

Documents to request

Each item should be received in writing before authorizing repair work.
  • Service record with technician notes
  • Diagnostic report listing propulsion, inverter, BMS, drive-unit, and high-voltage codes
  • Written confirmation of software versions before and after service

Pre-service evidence

Capture before drop-off. Once the vehicle leaves your possession, proving prior condition becomes significantly harder.
  • Photograph propulsion or high-voltage warning messages
  • Screenshot Polestar app errors or vehicle status inconsistencies
  • Note speed, road conditions, state of charge, temperature, and whether the event followed charging

Service advisor interaction

Operational notes specific to the conversation at the service desk.
  • Ask service to document propulsion-system findings separately from infotainment or app concerns.
  • If the issue cannot be reproduced, request written confirmation that historical codes were reviewed.
  • A software-only remedy should be documented with before-and-after software versions.
  • If charging behavior is cited as the cause, request written explanation of how propulsion components were evaluated.
  • Safety-critical propulsion concerns should not be closed with vague 'operating as designed' language.

Repair authorization

Cautions before signing.
  • Do not authorize paid propulsion or high-voltage diagnostic work until warranty classification is clarified in writing
  • If a high-voltage or drive-unit component is quoted, request written warranty determination before approval
  • Separate unrelated maintenance from propulsion-system work before approval
  • Review authorization forms carefully before approving additional repairs

Post-service verification

Complete before leaving the service location. Issues that surface after departure are operationally harder to attribute to the visit.
  • Confirm no propulsion, drive-system, or high-voltage warnings remain after a full drive cycle
  • Verify normal acceleration and power delivery during a short drive
  • If charging symptoms were related, verify charging behavior as well
  • Confirm software version and remedy are documented
  • Confirm the service record states whether the vehicle is safe to drive
  • Save the closed service record

Email templates

Documentation-focused templates for service correspondence. Tap copy to use. Subject and body are kept verbatim — paste them as-is into your email client.

Warranty notes

  • Polestar 2 propulsion, high-voltage, inverter, and drive-unit components should be evaluated under Polestar's applicable warranty terms for VIN (Vehicle Identification Number) [VIN].
  • Software-only remedies do not extend warranty unless Polestar states otherwise in writing.
  • Goodwill repairs do not extend warranty coverage. Confirm classification in writing.
  • Repeated propulsion warnings should be documented as recurring safety-related service history.

Observational patterns

Propulsion complaints should document speed, state of charge, temperature, drive mode, and whether the event followed charging or an OTA (Over-the-Air software update) update.

If the issue cannot be reproduced, historical-code review remains important because propulsion warnings can clear before inspection.

Reduced-power or stop-safely events should be documented separately from general software inconvenience.

This playbook covers

Related playbooks

Track this case

EVRiskIndex Cases is a forthcoming tool for owners to monitor their dealer and manufacturer interactions through a single case file — pre-filled email templates routed through our infrastructure, automatic thread preservation, evidence vault, and recall monitoring tied to your VIN. Coming soon.

If you would like to be notified at launch and invited to the free beta, send a message via our complaint and contact page with the subject line "Cases beta".

Already in an active dispute with a dealer or manufacturer? Use the file-a-complaint form to put it on the record with EVRiskIndex. All complaints are reviewed by editorial.