Use symptoms to decide the next action

Start here

For “Use symptoms to decide the next action”, what you notice. Likely first check. Do not do. Gradual output decline during dusty period. Compare weather/season and visible soiling. Assume an electrical failure immediately. Sudden persistent drop. Check inverter alerts, grid status and recent changes. Open DC equipment yourself. One module visibly damaged. Isolate through approved procedure and call service. Touch.

What applies to this exact problem

Check these first

• What you notice: Likely first check.
• Gradual output decline during dusty period: Compare weather/season and visible soiling.
• Sudden persistent drop: Check inverter alerts, grid status and recent changes.

Fix it in this order

1. What you notice: Likely first check.
2. Gradual output decline during dusty period: Compare weather/season and visible soiling.
3. Sudden persistent drop: Check inverter alerts, grid status and recent changes.
4. One module visibly damaged: Isolate through approved procedure and call service.
5. New roof leak after maintenance: Document location, weather and recent work.
6. Repeated inverter protection fault: Record code and obtain qualified diagnosis.
7. Compare weather/season and visible soiling.

Evidence to keep

• Signed quote and scope — keep it with the evidence for “Use symptoms to decide the next action”.
• Module/inverter serials and warranty — keep it with the evidence for “Use symptoms to decide the next action”.
• DISCOM/portal application IDs — keep it with the evidence for “Use symptoms to decide the next action”.
• Generation data, photos, and installer tickets — keep it with the evidence for “Use symptoms to decide the next action”.

Do not make it harder

• Paying the final amount before checking agreed milestones For “Use symptoms to decide the next action”, that can hide whether the underlying issue is actually resolved.
• Assuming low generation is automatically a bad panel For “Use symptoms to decide the next action”, that can hide whether the underlying issue is actually resolved.
• Treating installer completion as DISCOM/subsidy completion For “Use symptoms to decide the next action”, that can hide whether the underlying issue is actually resolved.

How you know it is fixed

• The official record and your real-world result agree for “Use symptoms to decide the next action”.
• You have enough written evidence to prove the issue is finished if it returns later for “Use symptoms to decide the next action”.

If this still isn't resolved

1. Installer/vendor grievance State the unresolved issue explicitly: “Use symptoms to decide the next action”.
2. DISCOM/portal grievance route State the unresolved issue explicitly: “Use symptoms to decide the next action”.
3. Consumer forum or other official remedy where appropriate State the unresolved issue explicitly: “Use symptoms to decide the next action”.

Parent-guide references

These references support the parent guide and escalation context. Verify provider-, model-, policy-, or jurisdiction-specific details before an irreversible step.

• National Rooftop Solar Knowledge Centre
• MNRE — Grid Connected Solar Rooftop Programme

Need the complete context?

This page solves one branch. The parent guide covers the full decision, edge cases, alternatives, and related checks.

Open the full guide