Skip to main content
Open Settings → Integrations, then select Events in the header to open the Events screen. Use Back to return to Integrations. The screen loads the latest account commands on entry. Scroll toward the end to load older events. Use the Refresh icon at the right of the header to reload the latest events; the screen does not poll for updates. Acceptance confirms that Liftx received the command, not a fill or closure.

​
Controls

A page error stops automatic loading. Use Refresh to retry from the latest events. Only one group can be expanded at a time. Its details are discarded when closed, when the list is refreshed, or when its parent leaves the retained history window. Each command card shows the action, the client command ID, last update time, and the available position ID and error code. A saved close/cancel request also shows its terminal sequence. Use the position ID to inspect the actual position and its orders in Liftx; the receipt card is not a position-balance display.

​
Status labels

Statuses use Liftx’s branded colors: green for handoff or observed execution, orange for expired commands or mixed outcomes, and red for rejection, outcomes needing review or errors. Pending admission and submission remain neutral. Color does not add execution evidence or prove a fill or closure. A Close request saved or Cancel request saved line proves the corresponding owner request and sequence were recorded. It does not mean that all orders are cancelled, exposure is flat, or the position’s lifecycle has completed.

​
Group termination

A group card identifies This setup’s positions or All Liftx positions on the target, its frozen target count, and counts by receipt status. Select View targets to inspect each captured position separately. At most 64 child targets belong to one group. A zero-target group can succeed with Execution observed and no child rows. That records an empty capture and its ordering fence. It does not prove there are no positions on the exchange, no other accounts with exposure, or no later OPEN signals. Group admission captures its membership once. Reading or refreshing it does not add newly opened positions or retry unsuccessful children.

​
Investigate a TradingView signal

  1. Confirm that the intended TradingView alert is enabled and triggered. Inspect its alert log and Webhook status.
  2. Open Liftx Events and select the Refresh icon. Correlate the setup/source and command identity from the generated message; ordinary alerts derive identity from source, UTC trigger second, and action.
  3. Read the receipt state and any error code. Inspect every target for a group.
  4. Inspect the actual Liftx position, orders, and remaining exposure.
  5. If the outcome is uncertain or delivery failed, manage remaining exposure deliberately. Do not create a new command identity merely to force a retry.
No row can mean that admission never succeeded; it is not a complete diagnosis of a network failure. Conversely, a missing response does not prove there was no accepted command. Use the TradingView troubleshooting guide and receipt contract. Resolved receipts are retained for 30 days. Unresolved work remains until resolution. Export records needed for a longer audit history through the scoped API; the Events screen is not a permanent archive.