Definition events
When you run a definition over history, every time its setup happened is kept as an event. Your plan caps how many events you keep in total, across all your definitions.
Free | Starter | Pro | Ultra | |
|---|---|---|---|---|
Definition events | None | 1,000 | 50,000 | 500,000 |
Free has no research, so it keeps no events.
What one event is
One event is one occurrence on one instrument and interval. Two years of BTC opening range breaks came to 786 events. The same definition over ETH as well adds ETH's breaks on top.
Events are what studies measure. A study reading them uses none of the allowance.
How running over history uses it
Each run adds the events it finds. What decides the size is how often the setup fires: a setup that happens several times a day fills the allowance far faster than one that happens once a week.
Running over dates that are already covered adds nothing. Chartnaut says Already collected, and an overlapping range scans only the missing part. That holds while the version and the settings stay the same.
A new version of the definition, or a profile with different settings, finds its events afresh. Those count on top of the old version's events until you delete the old ones.
See where you stand
Open Subscription from the menu under your name and choose the Limits tab. The meter labelled Collected events shows how many you keep. It refreshes at most once an hour; the limit itself always counts what is there now.
At the limit
A run you start with the allowance used up is refused before it begins:
You have reached the Collected events limit for your plan. Please upgrade to continue.
A run that reaches the limit partway stops. On the definition's Datasets card it shows Your plan's collection limit was reached. Upgrade to continue collecting. A run stopped this way adds nothing to the dataset, and it is not retried on its own.
When you have made room, click Delete run on the stopped run, then run the definition over those dates again. See Run a definition over history.
Free space
On the definition's Overview tab, in the Datasets card:
Click a dataset's trash button and confirm with Delete dataset. Every run and event for that instrument and interval goes, for the version and profile selected at the top of the page.
A run that stopped or failed has its own Delete run button.
Deleting the definition itself does not free its events. Delete its datasets first, then the definition.
If an app reads the definition, it runs it over its dates again the next time the app opens, and those events count again.