Locate the stage that failed
Check that the alert is active, its condition occurred, webhook delivery is enabled and the URL matches the saved Flipr.Cloud connection. Compare the exact delivered message with the intended one. Verify the account’s subscription, saved key label, market and environment.
Execution History shows recorded executions. An empty history alone does not prove the request never arrived: some requests are rejected before an execution record is created. Inspect the alert delivery status and error response too.
Check header, quantities and prefixes
Start with a symbol and the exact saved key label. Put // comments after the header on dedicated lines. Check total balance (%), free balance (%%) and position (%p) semantics in the Syntax Reference. SL/TP need valid prefixes; entry-relative values do not replace the prefix.
BTCUSDT on My_API_Key
balanceA successful balance response is a connection check, not an order qualification. Unknown tokens can be ignored, and an execution error can be followed by later commands. Inspect each command result.
A timeout is not a cancellation
Check before retrying
Processing may continue after the caller stops waiting. Inspect execution results, open orders and positions on the exchange before repeating a trading signal; repeating it can duplicate an entry.
Long waits can exceed HTTP timeouts. They are not a durable scheduled job and do not establish that an order filled. See Wait for the reviewed transport and restart limits.
Read the exchange error in context
Check permission, whitelist, account environment, available funds, instrument, quantity step and minimum size. Native protections, tags, reduce-only, hedge mode and trigger types differ by integration. Consult Exchange Quirks and Exchange Settings.
An entry can succeed while protection fails. Check the actual position and remaining orders. To close, use the relevant position command; cancelling orders alone does not close a position.
Keep evidence useful and private
Record the timestamp, account label, symbol, returned error and execution identifier. Keep credentials and personal webhook URLs out of screenshots or public support posts. Separate delivery time, processing time, order acceptance and fill time when investigating latency.