Order status is a Trigger type in FYERS Automate. It allows your automation to move forward only when a specific order (placed earlier in the same automation run) reaches the status you choose.
This trigger does not place orders by itself.
Use Order status when your next step depends on what happened to an order—for example, place a stop-loss only after an entry order is executed, or take a different action if an order is rejected or cancelled.
After adding this trigger, Automate continuously checks the selected order’s status. Once the order reaches the chosen status, the automation continues to the next connected step.
Triggers when a specific order is executed (completed in the market).
Example: Your automation places a buy order. You use Order execution to continue only after the buy order is executed, and then place a stop-loss order.
Triggers when a specific order is rejected.
Example: You place an order, but it gets rejected due to reasons like invalid parameters or insufficient funds. If you select Order rejection, the automation can move forward to a step like sending a notification or stopping the run.
Triggers when a specific order is in pending status (placed but not executed yet).
Example: You want the automation to take an alternate path if the order is still waiting in the market. Select Order pending to proceed when the order is confirmed to be pending.
Triggers when a specific order is cancelled.
Example: If an order is cancelled (by you or by the system), selecting Cancelled order lets the automation continue to the next step—such as placing a fresh order, sending an alert, or ending the automation.
The Order status trigger is configured on the canvas by selecting the trigger, choosing the specific order from your workflow, and selecting the trigger type you want to wait for (Order execution, Order rejection, Order pending, or Cancelled order).
| Scenario | What happens |
|---|---|
| I selected Order execution, but the order gets rejected | The automation will not move forward because the selected status (execution) was not reached. |
| I want different actions for execution and rejection | Use separate Order status triggers—one waiting for execution and another waiting for rejection. |
| I used Order pending but the order later gets executed | The trigger is met as soon as the order becomes pending. After that, the automation continues based on your workflow design. |
| I want the automation to respond when an order is cancelled | Select the Cancelled order trigger type so the automation continues only when cancellation happens. |
Last updated: 22 Dec 2025