@admin It looks like we are performing testing duties for you for free.
Why were the changes not tested before going live?
Who was responsible for this?
What action have you taken?
Absolutely bad experience from such a big broker. The worst reliability of all brokers we work with. Do something about it.
Technical explanation of the bug:
TOTP changes every 30 seconds. System or server time is used to calculate TOTP.
So if there is a difference in clocks of client & server, TOTP generated by client may not match with the server.
To safeguard from this, the server normally matches the TOTP entered by client with current TOTP & also with TOTP which was valid in the previous 30 seconds. This makes sure small differences (less than 30 seconds) in client & server do not affect the login.
Angel is likely only comparing it with current OTP & not comparing with OTP that has expired in previous 30 seconds.
Due to this the "Invalid otp" is coming sometimes & sometimes it is working.
We are sending this details to Angel. Hopefully they will fix it before tomorrow morning.
@StocksDeveloper Too many internal server errors in the logs.
STGN1003 @ 12:52:39
TZ7990 @ 12:52:38
HTTP Status 500 – Internal Server Error
This is totally unacceptable.........horrible experience guys.
On our platform many users are using Angel One API everyday.
Today all of a sudden many users are getting above error, have you changed API Limits by any chance?
If yes, roll the change back asap....it is affecting trading for many users.
Instrument master has symbol: BANKNIFTY26OCT2344500CE
Position data is returning symbol: BANKNIFTY23OCT44500CE
It started happening all of a sudden, was there any change made?
Please look into it urgently.
@admin users are saying that this is happening for future contracts & option orders are going through fine.
This is second day of the error.
So many accounts are affected by this major outage.
Error Message: Credentials wrong or login id not migrated to Smart API.. Angel error code: AB1007, Message: INTERNAL SERVER ERROR.
Account Number: R6880
Hello,
This issue only happens sometimes (not always) & it goes away after some time.
So today at around (2024-04-01 11:37:44.786 am); we could see that there was no margin data coming & then at around 11:40 it started coming again.
Sample Acc No: K631970
@Moderator_2 said in Reason for Rejection : 265:
As we verified, the error has been pushed from exchange. Kindly share us the API request/Scrip/Client code and issue date and time to clarify on which category the order has rejected by exchange.
3 days ago we gave you a screenshot which already had order id highlighted. That order id would have given you all the details you are asking; so I do not understand why are you asking it again??
Team,
There are 2 ongoing issues:
Sample account: RUCL1092
Our customers are also facing similar issues. Please see today's error details given below:
Angel ID: S281120
Order id & rejection reason visible on below screenshot.
It seems resolved now but check what happened. This is crucial & should not repeat.
It seems resolved now but check what happened. This is crucial & should not repeat.