I think there may be a bug with regards the history/job associations introduced in the upgrade. Many of the users have histories where the associated jobs are no longer shown. The histories themselves still exit. The problem seems to be mainly workflows with many jobs. The HistoryID/job association is still in the database, though there is no history/dataset association for these Histories (I havent investigated enough to know if this is expected).<br clear="all">
<br><div>This is definitely a result of the upgrade and is reported by a number of users. It does not occur for all histories - only some. The latest upgrade does not help.</div><div><br>Cheers<br>Dennis <br>
</div>