A continuous chart joins information across expiries; a specific futures contract identifies one expiry. Do not assume that a continuous chart label is directly accepted by your Rithmic connector or that changing its mapping transfers existing positions. Verify the resolved execution contract, the alert's saved context and the account's existing orders separately.
Educational software guidance. Trading involves risk. Read the financial and information disclaimers.
Compare the identifiers
| Identifier | Main use | Verification |
|---|---|---|
| Continuous chart label | Charting across successive expiries | Chart provider's roll/adjustment rules |
| Specific contract | One expiry's data or trading route | Product, month, year and exchange |
| Generator trading-symbol field | Selects or maps the recipient's intended execution instrument | Current service configuration and resolved result |
CME explains product/month/year codes. Formats can differ by platform. In this native lookup, ESZ6.CME resolved an ESZ6 quote row:
What to confirm for alert automation
- Record the chart symbol and timeframe.
- Record the running alert's saved script/input/chart context.
- Record the generator's selected trading symbol and documented mapping.
- Verify the specific contract resolved by the receiving service.
- Reconcile existing positions and orders before changing expiry-related settings.
TradingView's alert documentation states that changed chart inputs/context do not automatically update the saved alert snapshot. Do not assume changing the visible chart updates every active alert.
Read rollover claims in scope
PickMyTrade's rollover article recommends specifying the exact contract and describes its continuous-symbol transition rule. It also states that existing expiry positions remain the user's responsibility. The same document discusses planned improvements and current behavior; do not turn that into a universal guarantee that every product, account and alert automatically rolls correctly.
No continuous mapping or position rollover was executed here. Use the current generated configuration and a suitable permitted verification before relying on a particular mapping route.
Common questions
Does rolling a chart move my position?
Do not infer that. Existing positions and orders must be reconciled separately for their specific contracts.
Can ES1! be sent to any Rithmic application?
No universal support is established. Use the exact connector or bridge's current mapping rules.
Why can the chart and broker prices differ?
First check that they refer to the same product/expiry, session and data source. Continuous-series adjustments can also affect a comparison.
Must I recreate an alert after changing expiry?
For a script alert's saved chart/input context, follow TradingView's recreate procedure when that context changes. Also verify the receiving service's separate symbol settings.