JASMY detected but couldn't buy it

[RatFou]

Hey,

Got that in the logs:

2021-11-22 09:00:24,197 INFO: New coin detected: JASMY
2021-11-22 09:00:24,198 INFO: File does not exist, creating file
2021-11-22 09:00:24,198 INFO: Checking for coin announcements every 3 seconds (in a separate thread)
2021-11-22 09:00:24,198 INFO: New announcement detected: JASMY
2021-11-22 09:00:25,197 INFO: LATEST TRADE: JASMY_USDT | id=2192886784 | create_time=22-11-21 08:00:17.315000 | side=sell | amount=663.812 | price=0.223892
2021-11-22 09:00:25,198 INFO: starting buy place_order with : announcement_coin='JASMY' | globals.pairing='USDT' | volume=15 | amount=66.99658764046951 x price='0.223892' | side = buy | status='test_partial_fill_order'
2021-11-22 09:00:25,198 ERROR: 
2021-11-22 09:00:25,209 INFO: No coins announced, or coin has already been bought/sold. Checking more frequently in case TP and SL need updating

After that I got thousand lines with "No coins announced..."

Do you think it's because the order couldn't be filled?

[AdamHayton]

Unfortunately, same issue here.

2021-11-22 07:59:48,624 INFO: New coin detected: JASMY
2021-11-22 07:59:48,630 INFO: New listing detected
2021-11-22 07:59:48,631 INFO: Checking for coin announcements every 3 seconds (in a separate thread)
2021-11-22 07:59:48,632 INFO: New announcement detected: JASMY
2021-11-22 07:59:49,885 INFO: LATEST TRADE: JASMY_USDT | id=2192876546 | create_time=22-11-21 07:59:39.174000 | side=sell | amount=272.142 | price=0.150581
2021-11-22 07:59:49,886 INFO: starting buy place_order with : announcement_coin='JASMY' | globals.pairing='USDT' | volume=25 | amount=166.0236019152483 x price='0.150581' | side = buy | status='test_partial_fill_order'
2021-11-22 07:59:49,887 ERROR: 
2021-11-22 07:59:49,898 INFO: No coins announced, or coin has already been bought/sold. Checking more frequently in case TP and SL need updating
2021-11-22 07:59:49,909 INFO: No coins announced, or coin has already been bought/sold. Checking more frequently in case TP and SL need updating
2021-11-22 07:59:49,920 INFO: No coins announced, or coin has already been bought/sold. Checking more frequently in case TP and SL need updating
2021-11-22 07:59:49,931 INFO: No coins announced, or coin has already been bought/sold. Checking more frequently in case TP and SL need updating
2021-11-22 07:59:49,942 INFO: No coins announced, or coin has already been bought/sold. Checking more frequently in case TP and SL need updating

[AdamHayton]

We have no details for the error logged, should logging.error(e) provide more info? Are we missing something in the format string for the logging or do we need to pass a message rather than the exception itself? Should this really be using logging.exception('') method?