Skip to main content

Events page

The Events page is an audit/log view of operator actions and system-side updates (orders, executions, tracking, and corrections).

  • URL: https://mesolive.io/events

What Events are​

Each row is a server-side “breadcrumb” with:

  • Event Time (recorded in UTC)
  • Event Type (a structured enum)
  • Message (human-readable details; often the most important field)
  • optional references: Account / Strategy / Position / Leg ids
  • optional PnL

Events are extremely useful for troubleshooting, but they are not a replacement for broker-native order/execution logs.

What you can do here​

This is useful for troubleshooting fills, PnL changes, and tracking issues.

How to use the grid​

  • Start from the object you’re debugging:
    • filter by Position id (or Leg id) first, then narrow by Event Type.
  • Use Message filtering to locate a specific order group, broker, or workflow step (e.g. “Exit Position”, “Remove Legs”, “Marker-only”).
  • Increase page size when investigating longer sequences (Build → SendOrder → OrderReceived → executions → close).

Practical debugging patterns (operator runbooks)​

“Order didn’t show up at the broker”​

  1. Filter by SendOrder and read the message:
    • which broker/provider the order was sent to
    • what operation it was (AddPosition/AddLegs/RemoveLegs/ExitPosition)
    • which order group number was used
  2. If you’re using IBKR, remember that MesoLive may create orders in TWS that still require a transmit step (see Order Execution).
  3. Check for any subsequent OrderReceived events; if none arrive, the broker side may not be acknowledging/streaming order updates.
  4. Validate Agent connectivity: https://mesolive.io/agents, Troubleshooting → Agent.

“Fills/partials are not reflected in MesoLive”​

  1. Filter by OrderReceived and CreateExecution / AddExecutionToLeg.
  2. If executions exist but legs/positions still look wrong, inspect the affected leg:
  3. Use Data Explorer to confirm market data is fresh (stale greeks/prices can make PnL look wrong).

“Position closed unexpectedly (or won’t close)”​

  1. Filter by CloseLeg / ExitPosition / ReopenPosition.
  2. Read the message to understand whether it was:
    • a broker-driven execution/close, or
    • a local/manual tracking change (e.g. “Set Closed” workflows).
  3. Verify the actual broker state in TWS/TastyTrade and reconcile using Assign Legs / corrections if needed.

“Signals show Eval failed or vars don’t match expectations”​

  1. Look for UpdatePositionDefinedVars around the time the issue started.
  2. Confirm that market data is updating (missing greeks/quotes often leads to evaluation failures):

Event type reference (common ones)​

The Event Type field is a structured enum. The message is the authoritative detail; types are best used for filtering.

Strategy lifecycle​

  • CreateStrategy: a strategy container was created (manual or imported).
  • OverwriteStrategy: an imported strategy plan was overwritten.
  • RenameStrategy: the strategy name was changed in the Portal.
  • DeleteStrategy: the strategy and its tracked state were deleted from MesoLive’s DB (does not place broker orders).

Position lifecycle and execution tracking​

  • BuildPosition: a Build step started (structure selection / preview).
  • CreatePosition / CreateLeg / CreateContract: tracked objects were created in the live database.
  • SendOrder: an order group was sent (or executed locally for paper/marker-only groups).
  • OrderReceived: an order update was received/applied (or a local “filled” marker-only update).
  • CreateExecution: an execution record was created.
  • AddExecutionToLeg: an execution was attached to a specific leg.
  • ProcessExecutionPlan: the system processed an execution plan step (often shows up around order/marker workflows).
  • CloseLeg: a leg was marked closed.
  • ExitPosition: a position exit was recorded.
  • ReopenPosition: a position was re-opened (tracking correction).

Adjustments and corrections​

  • SelectLegForMoveLeg / SelectLegsForAddLegs: an adjustment selection was initiated.
  • MoveLeg: a move-leg adjustment was applied.
  • ReduceLeg: leg reduction workflow (often during remove/exit operations).
  • AdjustLegQtyByUser / AdjustLegAvgEntryPriceByUser: manual corrections from Position Tracking → Legs.
  • ChangeLegPriceAndQty / SetLegRealizedPnL: administrative corrections to leg state/PnL.
  • AdjustPositionRunningPnL: manual PnL correction applied at the position level.
  • UpdatePositionDefinedVars: position variables were persisted/updated (entry vars, adjustment var defines, Update Vars).

Paper trading​

  • CreateAccount: paper account created.
  • PaperAccountChange: paper account settings changed (commission/provider/etc).
  • PaperAccountReset: paper account reset (positions cleared; balance reset).
note

Some event types exist primarily for support/diagnostics and may be rare in normal operation.