Execution statuses

What each status of an executed command means, and what to do about it.

Applies to the Meanward Platform connectorOpen app

Every alert the connector receives ends with one status. You see it in the Telegram message (✅, ⚠️, ⏭️, 🚫 or ❌ in front) and in the cabinet under Trades → Signals. Most refusals come with the reason in words: the exchange's error, or the rule that stopped it.

Done

Status	Meaning	What to do
`filled` ✅	The order was filled. For an `open`, the TP order is on the exchange too.	Nothing.
`updated` ✅	The TP was moved to the new %.	Nothing.
`partial` ⚠️	The order was filled, but placing or moving the TP failed. The reason starts with "TP order failed" or "TP recreate after average failed".	The position is open without a TP on the exchange. Set one by hand, or wait: the next `update` or `average` places it again.
`pending` ⏳	Being executed right now.	Wait a few seconds. A `pending` that stays means the connector restarted mid-order; it checks such orders against the exchange by itself.
`test_passed` 🧪	A test signal from the cabinet's Check step went through: the alert was read, the account is on and the exchange accepted the key. No order was placed. A test that fails gets the status of what stopped it. Tests are marked Test in the log and never count in your statistics.	Nothing.

Skipped: nothing to do on the exchange

Status	Meaning	What to do
`skipped_already_open` ⏭️	An `open` for a pair and side that already has a position. Usually a repeated alert.	Nothing, unless you didn't expect a position there: then check the exchange.
`skipped_no_position` ⏭️	An add for a position that doesn't exist on the exchange.	Usually the position already closed (TP filled, closed by hand) or never opened. The strategy on the chart thinks otherwise: see "chart and exchange disagree" below.
`skipped_position_absent` ⏭️	A `close` or `update` for a position that's already gone.	Normal when the exchange TP filled before the strategy's close arrived.

Refused before reaching the exchange

Status	Meaning	What to do
`rejected_by_plan` 🚫	Your plan doesn't include this: an `open` or add on the Club plan or without a subscription, or a hedge command on Platform.	See plan limits. Closes and TP updates are never refused for this reason.
`rejected_tenant_suspended` 🚫	Your subscription isn't active (cancelled, expired or unpaid). Opens and adds are refused; closes and updates still go through.	Check Billing in the cabinet.
`rejected_by_risk_limit` 🚫	An `open` over the account's limit of positions per side.	Raise the limit (account card under Accounts, or `/set_long`, `/set_short`), or accept that this signal is skipped.
`rejected_exchange_disabled` 🚫	The account is switched off by you in the cabinet, or its exchange is switched off by me for everyone during an exchange incident. It gets no orders at all, closes included.	Check Accounts in the cabinet. If the account is on, it's an incident on my side; watch the Meanward channel.
`rejected_exchange_mismatch` 🚫	The alert names another exchange than the account of its URL (`?exchange=` or an `exchange` field). Refused for every command, closes included: a close meant for another exchange must not close this one.	Use the URL of the account you meant, or remove the extra `exchange` from the alert.
`rejected_account_over_limit` 🚫	An `open` or a hedge on an account over your plan's account limit, after a downgrade. Closes, adds and TP updates go through.	Remove an account or upgrade in Billing.

Refused by the exchange

Status	Meaning	What to do
`rejected` 🚫	The exchange said no. The message carries its code and text. Common reasons: the order is below the exchange's minimum size, not enough margin, the key lost its futures permission.	Fix the cause. An order below the minimum needs a bigger Volume (USDT). Not enough margin means the account is undersized for the cascade.

Errors

Status	Meaning	What to do
`parse_failed` ❌	The alert's body isn't a command the connector understands. Usually a custom alert message, or an alert created from the wrong script.	Recreate the alert with Any alert() function call and the message left as the strategy fills it. See TradingView alert.
`error` ❌	Something else went wrong; the message says what. Typical: an account removed while the signal was on its way; a pair the exchange doesn't trade or a quote currency other than USDT/USDC; on Hyperliquid, an `open` against an opposite position on the same symbol; a network or rate-limit failure after one retry.	Read the reason. Exchange outages pass; configuration errors don't, so fix the URL or the chart.

When the chart and the exchange disagree

The strategy on the chart doesn't know what happened on the exchange. If a command was skipped or refused, or if you touched the position by hand, the two drift apart: the chart may hold a position the exchange doesn't have, or the other way round.

To bring them back together: close the position on the exchange (or with /close_positions), then set Start time on the chart to now and recreate the alert. From that moment both start flat.