Configure the real generated copy
- Create a valid setup with OPEN and terminate and an approved small demo quantity.
- Generate Pine (advanced) → One-shot · scheduled demo in Liftx.
- Set a future OPEN time and a TERMINATE time at least 60 seconds later, before key expiry.
- After activation, enable the indicator and create Any alert() function call before OPEN time. Keep alert expiration after TERMINATE time and within credential lifetime.
- Observe both events in the provider log, Liftx Activity and the actual position.
0 idle, 1 waiting, 2 OPEN emitted, 3 termination emitted, 4 OPEN window missed. None of these values means accepted, filled, canceled or flat.
Complete source
Download the public Pine example.Before adapting the sample
The generated private copy replaces the dummytoken, link, catalog ID, source UUID, binding revision and liftxCredentialExpiresAt. Guided mode intentionally has an empty liftxOpenRequest; Liftx uses the saved opening configuration. Do not turn the public sample into a live sender by changing only its token.
Retain one ordered producer per setup, preserve event identities on delivery retries and never reuse a lifecycle reference for a new position. Pine setup, canonical command fields and target semantics explain the contract.
After any interruption, inspect Activity and actual positions, manage remaining orders/exposure and create a fresh source for a new alert. The example has no execution feedback, automatic delivery retry, automatic rearm or restart recovery.