Trading Signal Bot Events History
Publicerad den 6 aug. 2023Uppdaterad den 1 apr. 20252 min läsning
Contained in the table below is an all-encompassing reference to logged events that occur whenever you transmit your trading signals to OKX. The listing depicts a sequence of feasible actions and how they correlate with the messages visible on the user interface.
| 
     Event type
     | 
     Status
     | 
     Details
     | 
| 
     Signal Processing
     | 
     Success
     | 
     Processed entry signal and placed {cryptoPair} order
     | 
| 
     Signal Processing
     | 
     Success
     | 
     Processed entry signal and placed {cryptoPair} order with all available balance
     | 
| 
     Signal Processing
     | 
     Success
     | 
     Processed reverse entry signal and placed {cryptoPair} order
     | 
| 
     Signal Processing
     | 
     Success
     | 
     Processed entry signal and placed {cryptoPair} order with all available balance
     | 
| 
     Signal Processing
     | 
     Success
     | 
     Processed exit signal and placed {cryptoPair} order
     | 
| 
     Signal Processing
     | 
     Success
     | 
     Processed exit signal, but failed to place {cryptoPair} order due to position isn’t found
     | 
| 
     Signal Processing
     | 
     Failure
     | 
     Processed entry signal, but failed to place {cryptoPair} order due to position already exists
     | 
| 
     Signal Processing
     | 
     Failure
     | 
     {parameter} can’t be empty (50014)
     | 
| 
     Signal Processing
     | 
     Failure
     | 
     Incorrect type of {parameter} (51000)
     | 
| 
     Signal Processing
     | 
     Failure
     | 
     Processed entry signal, but failed to place {cryptoPair} order due to insufficient balance
     | 
| 
     Signal
     
     Processing
     | 
     Failure
     | 
     Failed to place order since the placed amount is not enough to purchase one contract of {cryptoPair}
     | 
| 
     Signal Processing
     | 
     Failure
     | 
     Failed to place an order for {cryptoPair} because a position or order already exists, and you haven’t enabled multiple positions in your settings
     | 
| 
     Signal Processing
     | 
     Failure
     | 
     Order failed,please check error code ({errorCode}) here
     | 
| 
     Signal Processing
     | 
     Failure
     | 
     Processed signal, but failed to place {cryptoPair} order due to position is being closed
     | 
| 
     Signal Processing 
     | 
     Failure
     | 
     Processed exit signal, but failed to place {cryptoPair} order due to message timeout
     | 
| 
     System Action
     | 
     Success
     | 
     Take-profit stop order for {cryptoPair} is successfully triggered
     | 
| 
     System Action
     | 
     Success
     | 
     Stop-loss stop order for  {cryptoPair} is successfully triggered
     | 
| 
     System Action
     | 
     Failure
     | 
     Take-profit stop order for {cryptoPair} failed to trigger
     | 
| 
     System Action
     | 
     Failure
     | 
     Stop-loss stop order for  {cryptoPair} failed to trigger
     | 
| 
     System Action
     | 
     Success
     | 
     Filled the trailing stop order of {cryptoPair}
     | 
| 
     N/A
     | 
     Failure
     | 
     For any other unexpected events, please refer to our official API Error Code here
     |