28 lines
1.7 KiB
JSON
28 lines
1.7 KiB
JSON
{
|
|
"type": "Execution Started Event",
|
|
"definition": {
|
|
"text": "The execution started event is the event that triggers the execution of a process. It usually references the execution finished event of another process on which the process depends on."
|
|
},
|
|
"paragraphs": [
|
|
{
|
|
"style": "Block",
|
|
"text": "Content"
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "These references determine when a process is due for another run. By listening to the execution finished event of the process it depends on, it may wake up just in time to process the new batch of data the dependency has just delivered."
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "Bots form a sort of multi-branched execution sequence with an indeterminate number of dependencies. Every time the bot further down the tree of dependencies finishes a cycle, it triggers the execution of multiple bots listening to its execution finished event."
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "In the context of a trading process instance running a trading session on the network hierarchy, the execution started event may be used to force the trading process to run only after the last indicator bot dependency finishes its job. This guarantees that all dependencies are up to date and that the trading bot will evaluate the information corresponding to the same candles for all indicators used by the trading system."
|
|
},
|
|
{
|
|
"style": "Text",
|
|
"text": "Not setting up this event on a trading session may result in eventual data inconsistencies, as—in theory—the trading bot may run with some indicators up to date and some slightly delayed."
|
|
}
|
|
]
|
|
} |