PickMyTrade Reverse Order Close: Close or Reverse?

PickMyTrade reverse order close controls how an opposite signal is handled, but you should define the desired final position before enabling it. A sell signal while you are long might mean close the long, reverse into a short, or follow an explicit strategy order. Those intentions need different execution rules.

This guide explains the distinction for PickMyTrade’s Tradovate automation. It explains indicator signals, TradingView strategy orders, repeated entries, and how to check execution. It is a decision guide, not a universal settings recipe: the official pages disagree on one disabled-reversal behavior, as explained below.

Key takeaways

• Define whether an opposite signal should close or reverse the position.
• Keep indicator reversal rules separate from explicit strategy entries and exits.
• Review repeated-signal settings and actual account size.
• Use an explicit close instruction when the intent is to exit.
• Verify both directions, fills, and protective orders in demo before enabling the configuration live.

Close or reverse: what is the difference?

Closing ends an existing position and leaves no exposure from that position. Reversing ends it and establishes exposure in the opposite direction. Write down the intended final position before configuring the alert. A direction label alone doesn’t tell the execution system whether you want an exit or a new entry.

These are hypothetical target outcomes, not reported executions. Notice that reversal size needn’t equal the old position size. The order sequence and quantity must be consistent with the route you use. Record the destination account and contract too; “flat” is only meaningful for the account and instrument being inspected.

What does PickMyTrade reverse order close do?

PickMyTrade’s stacking and reversal guide describes enabled reversal as closing existing opposite trades before opening the new direction. It discusses this behavior alongside pyramiding. Treat the generated settings as a connected configuration, then verify the resulting account position rather than judging success from a received alert alone.

For example, an indicator system might alternate between bullish and bearish regimes. Its intended response to a bearish event while long could be a complete switch to short. An exit-only system has a different intention: the same bearish event ends the long, while a separate entry condition determines whether any short should follow.

Documentation discrepancy: the FAQ describes disabled reversal as closing the existing position without opening the opposite side. The indicator guide’s configuration table describes disabled reversal as not automatically closing the old trade while processing the new signal. These descriptions differ. Confirm the applicable behavior for your generated setup and test it before relying on either interpretation.

The practical response is to avoid using a bare opposite buy or sell as an assumed close command. State the desired outcome explicitly and verify its supported message route. A toggle name cannot replace a clear exit design, particularly when additional sizing, duplicate-signal, or account-routing settings are involved.

Which PickMyTrade settings should you compare?

Compare reversal, repeated-entry handling, pyramiding, and account direction separately. Each controls a different part of the trade sequence. The table summarizes the linked product references; it does not certify every combination of settings. Keep the complete generated configuration when testing, rather than changing one flag in isolation.

Sources: FAQ, stacking guide, and advanced features guide. If a generated strategy configuration contains these fields, follow its own instructions; this indicator summary is not a substitute for that route’s setup.

Should you use an opposite signal or an explicit close?

Use a supported explicit close instruction when the purpose is to exit. Use a reversal workflow when the purpose is to establish a new opposite position after closing existing exposure. Separate these intentions in your alert design so a bearish condition doesn’t unintentionally become an entry when the account is already flat.

PickMyTrade’s FAQ identifies data: close as the close-command route. Generate the applicable message for your account rather than treating a two-field example as a complete order. Confirm whether your workflow closes the whole relevant position or uses supported targeted-close controls. Keep account, symbol, and routing scope explicit.

{
  "data": "close",
  "reverse_order_close": false
}

This is a syntax illustration of the command discussed in the FAQ, not a complete executable payload. It omits routing, authentication, and other generated fields. Don’t replace a working generated message with this fragment. Check the action and reversal settings within the configuration your actual integration produces.

Define close scope before using the command. The indicator guide describes a Close Alert as closing open positions/orders, but that wording alone does not establish account-wide cancellation or strategy-level isolation for every route. Resolve the following scope questions for the generated message. Do not infer them from an alert’s display name.

For targeted indicator exits, use the documented comment and full_closed workflow. Confirm its supported scope before using it alongside other entries. A successful position close does not, by itself, prove that every related pending order was cancelled.

Why do indicator and strategy alerts need different handling?

An indicator condition typically identifies an event; a TradingView strategy can generate its own entries, exits, and reversal transactions. Decide which component owns position management. Applying another reversal rule to an already explicit order stream can change the meaning of an instruction and make the external account diverge from the strategy.

The FAQ scopes its reversal explanation to indicator-based alerts and advises against relying on that setting for strategies with explicit entries and exits. Specialized strategy guides also contain configurations using reversal-related fields. Preserve the supported strategy workflow for your use case rather than transferring indicator settings or deleting strategy fields by assumption.

TradingView’s strategy documentation explains that an opposite strategy.entry() can reverse a simulated position. Its transaction size can include the quantity needed to close the old position. An order quantity and a final position size therefore answer different questions.

In TradingView’s broker emulator, moving from long 2 to short 1 can require a sell transaction of 3. Two units offset the long and one establishes the short. The following arithmetic illustrates net position changes; it is not a PickMyTrade JSON sizing recipe.

A route that closes the old position separately and then interprets the next quantity as a fresh entry needs different message semantics from a single netting transaction. Check how the supported integration interprets the emitted quantity. Passing a transaction size of 3 as a new-entry size could produce a different result from the intended short 1.

Review the strategy alert setup and inspect the actual outgoing payload. An order-action field and a market-position field convey different information. Don’t swap them merely because one example produced the direction you wanted. Check entries, exits, partial fills, and reversals as a sequence.

How do repeated signals and pyramiding affect the result?

Repeated same-direction signals determine how large the position becomes before an opposite signal arrives. Review this separately from reversal. PickMyTrade’s same-direction-ignore reference describes suppressing another same-direction signal when a position is already open. Disabling that control can allow additional entries in compatible configurations.

The important test is the quantity actually held at the broker. Imagine an initial long of one contract followed by another accepted long of one. Your exit now needs to account for two contracts. A close workflow designed around the first entry alone may leave exposure, while a reversal built around an assumed quantity can produce the wrong final size.

Also review the Pyramid control and the generated pyramid and same_direction_ignore values together. Public examples use different combinations for different workflows. Don’t treat every boolean as an interchangeable duplicate filter. Record the exact combination you tested, including what happened to any working orders.

Is reverse_action the same as reverse_order_close?

No. Direction inversion and handling an existing opposite position are different operations. PickMyTrade’s advanced features guide describes reverse_action for reversing trade direction on selected accounts. That is separate from deciding how an incoming signal handles exposure already present on the destination.

If one account receives the original direction and another receives an inverted direction, inspect both independently. Their starting positions, quantities, and order states may differ. A successful master-account reversal doesn’t establish that every routed account reached its intended final position. Keep each destination’s expected outcome in the test record.

What happens to stops, targets, and partial entries?

Include working orders in the handover between directions. After a close or reversal, inspect whether old stops and targets remain and whether new protection matches the remaining exposure. A flat position at one moment is insufficient if a stale working entry can open another trade later.

Partial closes need their own design. The targeted partial-close guide describes indicator-based routing using entry comments and a full-close control. It explicitly limits that workflow to indicator alerts. Don’t assume a strategy order ID or a familiar comment automatically provides the same isolation.

If you use multiple strategies on one Tradovate account, decide how their positions and exits interact on the same contract. A broad close or reversal can conflict with another strategy’s exposure. Check the documented scope of the selected command; don’t infer strategy-level isolation from an alert name.

How should you configure and test opposite signals?

Start with written expected outcomes, then generate the matching configuration and test one change at a time. Use a connected demo account and the intended alert route. Capture the starting position, event, received message, broker orders, final position, and remaining working orders. The table below is a test specification, not a claim that these tests were performed.

1. Choose close-only, reversal, or explicit strategy-order handling.
2. Confirm who owns exits: the script, the integration, or broker-held orders.
3. Open Generate Alert and review the supported route and account.
4. Record reversal, repeated-signal, sizing, and protection settings together.
5. Configure TradingView using the intended event source and message.
6. Run the relevant cases above and compare actual broker records.
7. Resolve any mismatch before enabling the route live.

Use PickMyTrade’s monitoring guide to inspect received alerts and execution records. Match timestamps and order IDs. If an exit fills but the replacement entry is rejected, the account can remain flat. If the close fails, don’t assume the intended reversal completed.

What should you check before changing a running setup?

Review open positions and working orders before changing alert logic. Record the old configuration and identify which route will manage existing trades during the switch. Stopping a TradingView alert doesn’t itself flatten Tradovate or cancel orders already submitted. Preserve required protection while you make the change.

If the change involves Pine code or strategy inputs, recreate the running strategy alert to capture the updated version. TradingView’s strategy alert documentation explains its independent saved copy. Retire obsolete alerts deliberately so the old and new versions don’t both send instructions to the account.

When troubleshooting, send support the exact generated settings with credentials removed, the starting position, alert timestamp and timezone, relevant order IDs, and the expected final position. “It reversed incorrectly” is harder to investigate than “long 2 before the alert; intended short 1; actual flat after these two orders.”

Frequently asked questions

Define the final position before automating the signal

Before enabling a running alert, record the tested account, symbol, settings, and expected handling of protective orders. Keep the test evidence with the configuration so future changes can be checked against the same cases. Follow the indicator setup guide for that route and verify your exact configuration in demo.

Disclaimer:
This content is for informational purposes only and does not constitute financial, investment, or trading advice. Trading and investing in financial markets involve risk, and it is possible to lose some or all of your capital. Always perform your own research and consult with a licensed financial advisor before making any trading decisions. The mention of any proprietary trading firms, brokers, does not constitute an endorsement or partnership. Ensure you understand all terms, conditions, and compliance requirements of the firms and platforms you use.

Also Checkout: Automate TradingView Indicators with Tradovate Using PickMyTrade