Fixed Issues

Previously, models imported using Model Hub displayed broken images on their Model Card. This issue is now resolved. The platform now applies a strict formatting override to reliably hide external markdown images that are inaccessible within the Cloudera AI context

Previously, following the introduction of pagination to the Jobs API, the parent job selection drop-down list only displayed the first 10 entries when scheduling a dependent job in projects with a high volume of workloads. This issue is now resolved. An optimized, paginated component now replaces the legacy dropdown list. This component fetches jobs in batches of 10 as a user scrolls down the list, significantly reducing backend API load. Additionally, a search filter is integrated into the new interface, allowing users to quickly locate and select from the entire list of available parent jobs.

Previously, following the introduction of pagination to the Jobs API, multiple UI interactions failed to process data beyond the first 10 results. This issue is now resolved. The Project Overview page now correctly supports pagination, and the system no longer triggers the misleading Unable To Get License Details error when handling dependent jobs outside the first page.

Previously, the Last worked on timestamp on the project listing page was previously updated by automated background events such as scheduled job executions, making the activity metric unreliable. This issue is now resolved, The timestamp now exclusively tracks actual user-driven activity, such as creating projects, modifying workloads, manually starting sessions, or performing file operations. Automated system processes and scheduled job runs no longer trigger an update to this metric.

Previously, some Spark Executor records contained null startTime variables, leading to a NullPointerException exception and causing those workloads to be dropped. This stemmed from logic that rewrote all failed executors to stopped, even when they had never started due to issues such as OOM errors or image‑pull failures.

This issue is now fixed. Additional fixes ensure that Kubernetes failure reasons surface correctly, interactive‑session executors inherit the proper session CRN, and sessions failing before pod creation are no longer excluded. These changes improve failure reporting and prevent workload records from being lost.

Previously, jobs were hard‑deleted from the database, leaving dashboard job‑run records without valid references and causing historical job details to display an empty workload_crn identifier. This behavior was inconsistent with sessions, applications, and models, which already use soft delete. This issue is now fixed. Jobs support soft delete through a new deleted_at timestamp. Deleting a job sets this timestamp instead of removing the row, and associated cron entries are handled the same way. Read paths exclude soft‑deleted jobs so they are no longer displayed in the UI, while the existing cleanup process still performs hard deletes after the configured retention period. This ensures historical job runs retain a valid workload_crn identifier even after the job is deleted.

Previously, updating the GPU or other resource settings on a stopped application correctly changed the accelerator_label_id key-value pair in the applications table. However, when the application was restarted, the previous GPU configuration was still used because the restart logic was reading stale values from the dashboards table instead of the updated fields in the applications table. This issue is now fixed. The field mappings are corrected so that updated GPU and resource settings now apply properly when applications are restarted.