NRUNO Trading Automation Wiki · Question 98

What should an automated trading status page show?

Infrastructure, Cloud & PerformanceLast reviewed: 25 Aug 2026
Short answer

A status page should separate public service health from private account state. Publicly show webhook/routing/platform incidents; privately show a user's cTrader connection and signal execution status.

What this means in practice

A status page should separate public service health from private account state. Publicly show webhook/routing/platform incidents; privately show a user's cTrader connection and signal execution status. This page is specifically about “What should an automated trading status page show?”, so each scenario below is explained by its own mechanism instead of sharing one generic diagnosis.

Real-world scenarios

Scenario A — Webhook outage

Separate platform-wide health from one user's execution route. A status page should identify the degraded component and time window while account-specific offline state remains visible to the affected user. For Scenario A — Webhook outage on question 98, use that evidence specifically to answer “What should an automated trading status page show?”; keep it separate from the evidence for the other scenarios on this page.

Scenario B — Platform incident

Separate platform-wide health from one user's execution route. A status page should identify the degraded component and time window while account-specific offline state remains visible to the affected user. For Scenario B — Platform incident on question 98, use that evidence specifically to answer “What should an automated trading status page show?”; keep it separate from the evidence for the other scenarios on this page.

Scenario C — User cBot offline

Reconnect is a reconciliation event. Re-read actual cTrader positions and pending orders first, then decide whether queued commands remain valid. Expire stale entries and make recovery idempotent. For Scenario C — User cBot offline on question 98, use that evidence specifically to answer “What should an automated trading status page show?”; keep it separate from the evidence for the other scenarios on this page.

What to check

  • intended signal/action
  • last stage that definitely succeeded
  • first stage that differs from intent
  • final cTrader state after the event

Practical rule

For “What should an automated trading status page show?”, change only the first layer whose evidence no longer matches the intended action. Preserve signal identity, timestamps and final cTrader state, and reproduce execution-affecting changes on demo before live use.

Decision summary

Direct answer: A status page should separate public service health from private account state. Publicly show webhook/routing/platform incidents; privately show a user's cTrader connection and signal execution status.

Next action: Match the observed evidence to one scenario above, test that mechanism independently on demo and keep the result traceable with one signal ID.

Primary sources

Need a TradingView → cTrader execution route?

NRUNO routes your TradingView instructions to cTrader. Your strategy and signal logic remain yours.