@jaideep-siddula You missed in my post I mentioned " I have set timeout to 30 seconds in SmartConnect.py still getting these errors." You are right infra may fail but should not fail this frequently for such critical financial applications. I got timeout errors 9 times on 12th April. Your timeouts may cause losses and may result in heavy losses if the position is not exited on time. And since this error is happening with a lot of folks who are using Angel APIs it is for sure something on Angel side which needs improvement if you want customers to stick with you.
techbytecache
@techbytecache
Best posts made by techbytecache
-
RE: ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x0000024771931880>, 'Connection to apiconnect.angelbroking.com timed out. (connect timeout=7)'))
-
RE: Internal Server Error while placing an order
Getting this error randomly since yesterday -
File "C:\Users\Administrator\AppData\Local\Programs\Python\Python311\Lib\site-packages\SmartApi\smartConnect.py", line 285, in placeOrder
orderResponse= self._postRequest("api.order.place", params)['data']['orderid']
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^
TypeError: 'NoneType' object is not subscriptable
Latest posts made by techbytecache
-
RE: Migration of SmartAPI to Angel One Domain
Seems this has impacted GTT orders. Can you check? Posted on other threads too but no one responding. Client codes -- V266489 and L61199814.
[E 240902 20:01:40 smartConnect:246] Error occurred while making a POST request to https://apiconnect.angelbroking.com/rest/secure/angelbroking/gtt/v1/ruleList. Error: Something Went Wrong, Please Try After Sometime. URL: https://apiconnect.angelbroking.com/rest/secure/angelbroking/gtt/v1/ruleList, Headers: {'Content-type': 'application/json', 'X-ClientLocalIP': '127.0.0.1', 'X-ClientPublicIP': '..147.98', 'X-MACAddress': '38:7a:::1a:*', 'Accept': 'application/json', 'X-PrivateKey': '*****', 'X-UserType': 'USER', 'X-SourceID': 'WEB'}, Request: {'status': ['NEW', 'ACTIVE'], 'page': 1, 'count': 50}, Response: {'message': 'Something Went Wrong, Please Try After Sometime', 'errorcode': 'AB1004', 'status': False, 'data': None} {'message': 'Something Went Wrong, Please Try After Sometime', 'errorcode': 'AB1004', 'status': False, 'data': None}
-
RE: AB1004 Something Went Wrong, Please Try After Sometime Since Aug 31
@Moderator_3 It's not working for V266489 and L61199814 since weekend. Is anyone looking into it?????
-
RE: AB1004 Something Went Wrong, Please Try After Sometime Since Aug 31
@Moderator_3 I too am facing same problem since weekend. I too thought it's due to maintenance but even today getting same error.
I am getting this error for Client Codes V266489 and L61199814.It's strange we are being asked for Client Code for error seen by so many people starting around the same time this weekend
-
RE: Error code AB1004 into gttlist() API for last 2 days
@Moderator_3 I am getting this error for Client Codes V266489 and L61199814
-
RE: Error code AB1004 into gttlist() API for last 2 days
@Moderator_3 I too am getting same error for all GTT api since last two days on my two Client ids. Do I need to share client IDs here on the forum for resolution??????
[E 240902 20:01:40 smartConnect:246] Error occurred while making a POST request to https://apiconnect.angelbroking.com/rest/secure/angelbroking/gtt/v1/ruleList. Error: Something Went Wrong, Please Try After Sometime. URL: https://apiconnect.angelbroking.com/rest/secure/angelbroking/gtt/v1/ruleList, Headers: {'Content-type': 'application/json', 'X-ClientLocalIP': '127.0.0.1', 'X-ClientPublicIP': '..147.98', 'X-MACAddress': '38:7a:::1a:*', 'Accept': 'application/json', 'X-PrivateKey': '*****', 'X-UserType': 'USER', 'X-SourceID': 'WEB'}, Request: {'status': ['NEW', 'ACTIVE'], 'page': 1, 'count': 50}, Response: {'message': 'Something Went Wrong, Please Try After Sometime', 'errorcode': 'AB1004', 'status': False, 'data': None}
{'message': 'Something Went Wrong, Please Try After Sometime', 'errorcode': 'AB1004', 'status': False, 'data': None} -
Error in GTT Create and Update
I am getting error from gttModifyRule and gttCreateRule since last two days. Nothing changed on my side
*** SmartApi.smartExceptions.DataException: Couldn't parse the JSON response received from the server: b"<html><head><title>Request Rejected</title></head><body>The requested URL was rejected. Please consult with your administrator.<br><br>Your support ID is: 13994946*********9185088<br><br><a href='javascript:history.back();'>[Go Back]</a></body></html>"
-
RE: ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x0000024771931880>, 'Connection to apiconnect.angelbroking.com timed out. (connect timeout=7)'))
@jaideep-siddula You folks don't read user posts properly. See @Mnagesh has already mentioned "in spite of talking care of rate limites and exception handling"
-
RE: ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x0000024771931880>, 'Connection to apiconnect.angelbroking.com timed out. (connect timeout=7)'))
@jaideep-siddula You missed in my post I mentioned " I have set timeout to 30 seconds in SmartConnect.py still getting these errors." You are right infra may fail but should not fail this frequently for such critical financial applications. I got timeout errors 9 times on 12th April. Your timeouts may cause losses and may result in heavy losses if the position is not exited on time. And since this error is happening with a lot of folks who are using Angel APIs it is for sure something on Angel side which needs improvement if you want customers to stick with you.
-
RE: ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x0000024771931880>, 'Connection to apiconnect.angelbroking.com timed out. (connect timeout=7)'))
@jaideep-siddula I understand what you are saying and meaning of the error but that doesn't answer why every other day we get TimeOut errors from your servers. You can see from my logs it happened multiple times yesterday. Also want to share it worked very well today with no timeout whole day. You need to look at increasing your infra etc to be able to take on the incoming traffic without getting unresponsive.