This apparently was an issue last year and it should NOT have been bug this again this year. Any ETA on the fix?? Thanks.
