@Pancan There is a problem on Schedule K that is causing this issue. The product development team is working on it, and they hope to have an update with a fix out by the end of the week.
