Manual port reconstitution resets next rebalance date

For two ports using semi-automatic reconstitution and rebalancing, where only a reconstitution was due today:

I chose “Reconstitute” and performed “Get Recommendations” followed by “Commit.” When I committed the recommended transactions, the next rebalancing date reset as though I also rebalanced today. Shouldn’t the next rebalancing date remain unchanged when only performing a reconstitution?

Bump. The same problem occurred again today for a manual reconstitution without a rebalance. The rebalance date was moved forward.

The rebalance date was also moved forward for a port that automatically reconstituted due to no recommended changes, even though a rebalance was not due.

This is still a problem for a port that reconstitutes weekly and rebalances every three weeks. I have to check actual transaction dates for the last rebalance to estimate if one is due.

It looks like this problem has been there since it was first implemented.
I’ve made the appropriate changes, and the update will be available shortly.

Thank you, Aaron. The next test for me will be next Monday.

I don’t believe the problem is corrected. Has the code changed yet?

The rebalance date was moved forward for a port that automatically reconstituted due to no recommended changes, even though a rebalance was not due.

You’re right. The change has not been pushed to the server that runs automatic rebalance. We’ll try to get it set for the 15th.

Because we weren’t able to get the proper testing done on the rebalance code pending release (which has other changes), this will be delayed until the 22nd. Sorry for the inconvenience.

Thanks for the status, Aaron!

Wth my latest reconstitution (accurate but sounds inappropriate), the rebalance date was properly left unchanged. It seems to be working as expected now, at least for rebalance periods longer than reconstitution periods. Thanks Aaron!