Understanding Warnings
Warnings are part of the result itself. They are there to show where the scenario is sensitive, incomplete, near a limit, or dependent on assumptions that deserve more care before the output is used for real planning.
Why warnings exist
GridGap is designed to be useful without pretending to be final. That means the app does not hide uncertainty. If a scenario relies on generic assumptions, pushes a component hard, or sits close to a practical limit, the warning system is there to say so.
A warning does not automatically mean the result is wrong. It means the result should not be read casually. Some warnings are light reminders to review an assumption. Others are stronger signs that the scenario may need changes before it can be treated as a comfortable planning result.
How warnings appear in the app
Warnings are stored with the saved result. On the results page, they are visible in two ways. First, scenario cards can show a warning count so you can spot scenarios that deserve extra attention. Second, the dedicated Warnings tab groups the warning list by severity.
This is important because warnings belong to the version and scenario you are looking at. If you switch versions, you are also switching to that version's stored warning set.
Common warning themes
In practice, warnings often cluster around the same kinds of issues. One group is assumption-related. This includes situations where defaults are still carrying too much of the scenario and the result would benefit from more specific real-world input.
Another common group is performance stress. This includes heavy battery depletion, thin reserve, aggressive recharge expectations, or inverter loading that leaves less comfort margin than you may want.
Solar scenarios can also produce warnings around weather sensitivity, panel-count cleanup, or controller-side limits. Installation guidance can raise its own cautions where cable runs, current levels, environment, or protection choices deserve more attention.
Warnings can also reflect missing confidence rather than outright danger. A result can be mathematically consistent and still produce warnings because the app wants you to treat it as provisional until more detail is known.
How to read them properly
Read warnings alongside the metric cards, not after them. A battery count, inverter size, or panel count may look neat on the Overview tab, but the warnings often tell you whether that neat answer rests on fragile ground.
A useful habit is to ask a simple question for each warning: does this change my confidence in the result, or does it only tell me what to validate next? Sometimes the answer is that you need to adjust the scenario immediately. Sometimes the answer is that the result is still directionally useful, but needs proper real-world checking before it informs a purchase or installation decision.
If several warnings point at the same subsystem, treat that as a pattern, not as noise. Repeated battery warnings usually mean the storage side needs another look. Repeated charging or solar warnings usually mean the recharge path is under pressure.
When warnings should slow you down
Warnings matter most when the scenario is already close to a decision point. If you are just exploring rough possibilities, a result with some warnings can still be useful as a comparison tool. If you are narrowing equipment choices, preparing a client discussion, or thinking about a real installation, warnings should carry much more weight.
For homeowners, warnings are a strong reminder that professional review matters before acting on the output. For installers, they are a prompt to validate the scenario more carefully and not treat the calculator as the final word.