Automations let a trader define rules for signal review, alerting, and controlled execution. The page should read like an operations workspace, not a marketing dashboard.Documentation Index
Fetch the complete documentation index at: https://docs.polychads.app/llms.txt
Use this file to discover all available pages before exploring further.
Core states
| State | Meaning |
|---|---|
| Draft | The rule is being configured and should not execute. |
| Dry run | The rule evaluates conditions but does not place trades. |
| Live | The rule can act within the configured limits. |
| Paused | The rule is retained but inactive. |
Rule setup
Each automation should make the active market scope, wallet scope, trigger, action, and risk limit clear before it can go live.Run ledger
The run ledger should show useful product state:- trigger matched
- skipped by risk limit
- skipped by market status
- skipped by balance
- order submitted
- order failed with recoverable reason