Website of Vivek Kumar Malviya · Not the official website of Angel One Ltd.Never share OTP or PIN · Stay safe →
Vivek Malviya.Authorised Person · Angel One Ltd

Order lifecycle and uncertain states

Requested quantity and confirmed position must never be confused.

Separate the states

A local intent may become a submitted request, acknowledgement, working order, partial fill or terminal state. Rejections and cancellations have distinct meanings. A request timeout means the local system may not know what happened; it does not prove the exchange rejected the order.

Store stable identifiers and reconcile with the authoritative broker records. A retry should follow a deliberate duplicate-prevention and reconciliation policy. A label such as “sent” is insufficient proof of a position.

One hundred requested, forty filled

A fictional 100-unit request receives confirmation for 40 filled units. The confirmed position is 40. There may still be 60 working units, or they may later be cancelled or filled. A cancel request is not a cancel acknowledgement; fills can occur during the cancellation process.

Handle uncertainty explicitly

If an acknowledgement is missing, block dependent assumptions and investigate the order state. Blind resubmission can create duplicate exposure. The explorer below only changes educational labels and sends no order or API request.

Diagram: process at a glance

Intent recorded → Request acknowledged → Fills reported → Position reconciled

Check your understanding

After a timeout, is resending the same quantity automatically safe?

No. The first request may have succeeded. Reconcile its state and apply duplicate protection before deciding what happens next.

खाता खोलें →WhatsApp →
ACCOUNT OPENING HELP

आपकी शुरुआत यहाँ से होगी।

यह केवल डिज़ाइन का नमूना है। आपका मोबाइल नंबर कहीं भेजा या सेव नहीं किया गया। असली प्रक्रिया देखने के लिए नीचे मौजूदा वेबसाइट खोल सकते हैं।

असली प्रक्रिया समझें →
FIND YOUR WAY

आप क्या ढूँढ रहे हैं?

Search articles, guides and account help.