Start with the broker record
Check the order’s exact rejection message, contract, quantity and time. Causes can include insufficient margin, product permissions, an ineligible contract, session restrictions or account limits. A model trade does not guarantee your account can execute it.
Resolve the cause first
Ask the broker about its rejection and current requirements. Inspect any other filled or working orders before submitting a replacement. Reducing scaling or adding funds is not proof that an earlier order was retried.
A missing opening may require explicit action
Do not expect repeated automatic attempts until the order succeeds. Once the cause is resolved, review the supported synchronization control and current exposure. A retry can use a different price and can be rejected again.
Give support a specific event
Include the strategy, masked account identifier, full contract, order reference, quantity, rejection message and timestamp with time zone. Keep passwords and API keys out of the report.
Questions about this guide
Does a broker rejection cancel my service?OpenClose
Not automatically. An order rejection, service billing and trading permissions are separate states. Check the specific broker reason and confirmed service status.
Will the provider keep retrying the missed order?OpenClose
Do not assume continuous opening retries. Resolve the rejection, check existing orders and use a supported explicit ReSync only after reviewing the intended exposure.
Will a rejected opening keep retrying automatically?OpenClose
Do not assume repeated retries. Resolve the broker’s reason, inspect existing orders and review the supported synchronization action before authorizing another attempt.