Live trading fails with issues in QR

##code that was working started to fail a few weeks ago with the following errors in quantrocket

2021-02-01 10:57:28 quantrocket.zipline: INFO [a13v_sieg] Trading a13v_sieg in account DU2761432
2021-02-01 10:57:29 quantrocket.zipline: ERROR Traceback (most recent call last):
2021-02-01 10:57:29 quantrocket.zipline: ERROR File “sym://qrocket_log_py”, line 34, in wrapped
2021-02-01 10:57:29 quantrocket.zipline: ERROR File “sym://qrocket_qrzipline_trade_trade_py”, line 62, in mule_trade_algo
2021-02-01 10:57:29 quantrocket.zipline: ERROR File “sym://qrocket_qrzipline_trade_trade_py”, line 184, in trade_algo
2021-02-01 10:57:29 quantrocket.zipline: ERROR File “/opt/conda/lib/python3.6/site-packages/zipline/algorithm.py”, line 669, in run
2021-02-01 10:57:29 quantrocket.zipline: ERROR for perf in self.get_generator():
2021-02-01 10:57:29 quantrocket.zipline: ERROR File “sym://qrocket_qrzipline_trade_algorithm_py”, line 41, in get_generator
2021-02-01 10:57:29 quantrocket.zipline: ERROR File “sym://qrocket_qrzipline_trade_execution_py”, line 181, in get_orders
2021-02-01 10:57:29 quantrocket.zipline: ERROR AttributeError: ‘float’ object has no attribute ‘lower’
2021-02-01 10:57:29 quantrocket.zipline: ERROR

Based on the traceback, I believe this means that Zipline is retrieving an order which has not yet been assigned an order status by the broker, and Zipline is not prepared for that (it’s expecting a string order status such as “New” or “Filled” and got Nan). We will have a fix for this in the next release.

In the meantime, if you query your order statuses I bet you will find a null Status on one of them. When that receives a Status, the error should go away.