Where to find this
Flow is the card titled Flow on the main dashboard (`dashboard.html`). It is visible directly under the Tasks card.
Flow and Transparency
What Flow explains and how to use it
Flow is the human-readable activity stream in Chilla. It helps you answer two questions quickly: what happened, and why it happened.
What you will see
- Flow action buttons: Replay logs, Expand Flow, Download logs.
- Category chips: All, Entry, Exit, Pass, Warn, Live.
- Per-event status pills: ENTRY, EXIT, PASS, WARN, LIVE.
- Summary counters above the feed for Entry, Exit, Pass, Errors, and Live.
ENTRY
EXIT
SKIP
LIVE
What each major element means
| Element | Meaning | What to do next |
|---|---|---|
| Entry event | Chilla opened activity within your boundaries. | Confirm account and task are the expected ones. |
| Exit event | A tracked activity was closed. | Review sequence around the event if you need context. |
| Passed event | System stepped aside with a specific reason such as task boundaries, or account minimum. | Open event details and compare with your selections and account readiness. |
| Warning event | Validation or account warning event was recorded. | Use troubleshooting steps and include the warning title in support requests. |
| Live event | Monitoring update without an entry/exit action. | No action needed unless the update conflicts with your expected setup. |
Common skip reasons and app wording
| Flow reason code | User-visible headline |
|---|---|
insufficient_balance | Entry paused by available resources |
broker_minimum | Entry paused by account minimum |
not_authorized | Entry paused by task boundaries |
validation_failed | Action paused by validation check |
risk_cap_exhausted / risk_cap_approaching | Entry paused by comfort boundary |
What you can do here
- Filter event categories with the Flow chips.
- Open Replay logs and load history by Last hour, Last 24 hours, Last 7 days, Last 14 days, Last month, All available history, or Custom range.
- Open details for a single event using the Flow details view.
- Download filtered logs as `chilla-flow-YYYY-MM-DD.pdf` or `chilla-flow-YYYY-MM-DD.json` from Download logs.
- Use Flow first when troubleshooting no-activity, passed events, or warnings.
What Flow explains, and what it does not expose
Flow explains
- What happened.
- Why Chilla responded at a high level.
- What action was taken or safely passed.
- Which task context was involved.
Flow does not expose
- Proprietary threshold values.
- Exact pattern and validation internals.
- Internal formula details.
- Private sequencing mechanics.
Flow FAQ
I expected activity but Flow is quiet. Is that a problem?
Not always. A quiet period can mean no valid conditions, active monitoring, or step-aside behavior within your boundaries. Check task status, account readiness, and capacity first.
Can Flow be used for support requests?
Yes. Include recent event timestamps, event types, and any warning labels when you contact support.