Short answer
Your multi-time-frame indicator usually repaints because it is reading higher-timeframe data in a way that lets unfinished information influence the lower-timeframe chart. Once the higher-timeframe candle closes, the chart looks cleaner in hindsight than it did live.
The three most common causes
- using higher-timeframe requests without thinking through confirmation timing
- mixing chart-timeframe logic and HTF logic into one visual state without clear gating
- sending alerts from states that are not stable at the moment the trader would act
How I usually fix it
The fix usually starts with deciding what the higher-timeframe layer is allowed to confirm, when that confirmation becomes valid, and whether the indicator should wait for bar-close stability or expose an early but explicitly provisional state.
- audit every higher-timeframe request and its intended timing
- separate provisional states from confirmed states
- retest the alert flow after the chart logic is repaired
- prefer honest late signals over flattering unstable ones
If your indicator looks impressive in hindsight but behaves differently live, the clean next step is Pine Script audit and repair or a direct message on WhatsApp.
WhatsApp for a 3-minute quoteFrequently asked questions
Does every MTF indicator repaint?
No. The problem is not the idea of higher-timeframe logic itself. The problem is how and when that data is used.
Can repainting be fixed without changing the look of the script?
Sometimes yes, but the visual behavior often changes slightly because the dishonest early states are removed or made explicit.
References
If you want to turn this topic into a real build or a clearer plan, send the setup on WhatsApp. You can also review the Work and Proof pages first if you want examples before you message.