another bug that weaseled its way into my positions today that i detect for the first time in 9 months.

so for every group of wallets (which i call portfolio), I have a model allocated to it. each model has its own iteration, so that i can keep track of changes within that model and everything is logged.
on any day the desired positions are logged into my database according to their portfolio, model, iteration, etc.
but i havent done much of turning old models on/off within a specific portfolio. id just deactivate the portfolio and start a new one.
apparently, the the LIVE positions were being merged with the model's output positions but NEVER took into consideration the iteration of the model, because once again, when i built it, even though i set in the db an identification for that iteration, I wasnt thinking about changing iterations for specific portfolios.
so when the model ran, now with a different iteration from yesterday, the positions from today and yesterday were merged and the stale position that shouldnt be on todays model, found a pairing on the stale iteration thats no longer used, so never triggered an exit.
i actually found this by accident today but wont happen again as I set a new control for this.
sometimes you just gotta figure out as you move and do things.
not big damage, but things like these break all the time. maybe skill issue on my part but it happens to me often.