Automation square off didnot honor exit time mentioned

Hi Team,

My Overnight automation strategies square off time did not honor the exit time i configured, one didnot exit and another exited at wrong timing.

let me know if you need more details.

Thanks

Hi @THtx4WANEV, could you please share the automation ID or name, along with the relevant details? This will help us investigate the behaviour further.

following are the ids, it was supposed to exit at specific time, nifty was squared off as soon as market opened and sensex it never sqaured off so i had to stop and start the automation
nifty - d3702165-c6c4-4fad-a1e0-f7ff863d6fde
sensex - b939fb91-2f8e-43b1-8fa4-e56d02a7837b

Hi @THtx4WANEV, we’ve reviewed both automation strategies. Here’s what we found:

NIFTY Strategy

It’s configured with a Wait node until 09:15, followed by a Square Off Position node.

  • The NIFTY 22750 PE order was placed at 2:03 PM on 26 October and remained open overnight.

  • On 27 October, when the Wait node triggered at 09:15 as configured, the square-off was executed.

The NIFTY strategy worked as expected.

SENSEX Strategy

It’s configured with a Wait node until 09:35, followed by a Square Off Position node.

  • On 26 October, the strategy started at 09:15. Since there were no open positions at that time, the Wait node completed its execution.

  • The SENSEX 72800 PE order was placed at 3:13 PM on 26 October and remained open overnight.

  • Since the Wait node had already completed at 09:35 AM on 26 October, it did not trigger again the next day. As a result, the position was not squared off.

  • The automation did not have a Stop Automation node, so the strategy continued running, but the completed Wait node was not reset for the next trading day.

  • The stop-loss configured while placing the order also did not trigger, as the LTP was below the buy average price of ₹374.35.

The SENSEX strategy behaved as configured based on our analysis.

Thanks @kGRGEpOlJ1 For the detail analysis, i got the problem where it lies now will correct it, thanks.