Copy the complete HMS code, all four groups, and the exact message from the P2S screen or Bambu Handy. Searching only the first digits, for example just 0300, can point you to a different fault than the one your printer is actually reporting.
Look up that exact code in Bambu Lab’s P2S-specific HMS wiki section, not a P1S or X1 article. The alert framework is shared across the whole P-series, but individual codes and thresholds are documented separately for the P2S.
Check simple causes first: an obstruction in the nozzle or filament path, a loose connection named in the alert, exhausted AMS 2 Pro desiccant, or a filament path that cannot move freely. Many HMS codes clear once the underlying mechanical cause is fixed.
Do not keep clearing the alert just to push a print through when it concerns heating, a fan, toolhead communication or mains power. Stop the printer, let it cool, and follow the service boundary described in the official article for that code.
When a fix does not hold, export logs from the printer and include the firmware version, the full code and the exact action that triggers it. That information is more useful to Bambu Lab support than a repeated factory reset and hoping the code does not come back.
Many HMS alerts trace back to routine upkeep rather than a hardware fault, so the P2S maintenance schedule is worth checking before assuming the worst. If the code specifically points to the hotend or heater, the nozzle and hotend replacement guide covers what can safely be done at home. The same four-group HMS format is used on Bambu’s other current printers, including the dual-nozzle X2D and H2D.