What the trader should do first
If the trading room, data rail, or copier behaves unexpectedly during a position, the first instruction is operational, not rhetorical: stop sending fresh orders and capture the incident immediately.
Back to help center
Program operations
Platform issues, order IDs, and support escalation
Learn how Mayospell handles room incidents, what evidence a trader should capture, and where desk support stops when the issue lives in local automation.
Updated July 5, 2026
What evidence belongs in the ticket
Mayospell treats support like a desk workflow. The trader should attach the seat, time of failure, exact Order ID, screenshots, and the exported room evidence pack so the reviewer has something concrete to inspect.
- Order ID and seat
- Time of incident
- Screenshot or screen capture
- Exported fills, notes, and room evidence bundle
Where desk responsibility ends
The platform can acknowledge account state, API access, and room logs, but it should be explicit when a failure belongs to third-party code running on the trader's own device rather than to the desk itself.