I have seen a similar behavior but not due to any kind of upgrade. When I have seen this, it has been due to the associated package not existing anymore or when a task was created and the package name is not current meaning it was renamed by another user and the current user hasn't refreshed the console to see the change. The only way I was able to get the task to function was to go into the DB and assign the task a package idn.
↧