ILAP Analytics – Release Notes v2.4.0.0

Modified on Sun, 7 Dec at 11:16 PM

Release Date: December 5, 2025
API Version: 2.4.0.0
Web UI Version: 2.4.0.0
Background Job Version: 2.4.0.0


Overview

This release introduces several enhancements and fixes across the ILAP Analytics API, Web UI, and Background Jobs. It also includes an update to the deployment (Bicep) templates to improve configuration and reliability.

Pull Request: PR 3097 – ILAP Analytics Release 2.4.0.0


Infrastructure & Deployment Changes

Bicep Template Update

A new configuration parameter has been added to the Bicep templates:

  • backgroundJobAppUrl – Specifies the base URL of the Analytics Background Jobs App.

Example:

backgroundJobAppUrl: 'https://app-ilapanalytics-backgroundjobs-dev.azurewebsites.net'

You can find the correct URL by navigating to the Background Jobs App Service in Azure and selecting Browse.


Completed Work Items

4133 – Delete One Schedule from a Report Schedule

Users can now delete an individual schedule within an existing report schedule, allowing more fine-grained control over scheduled reports.

4306 – Identify Source/Sender of Received Schedule

The system now allows identifying the origin (source or sender) of received schedules, improving traceability and auditability.

6336 – View History in Progress Summary

Enhancements have been made so that users can view historical information within the progress summary, giving better insight into past processing activities.

6712 – Improvement of Health Check for ILAP Analytics

Health checks have been improved to provide more accurate and detailed diagnostics about the overall system state.

7050 – Update IDE Progress from Background Jobs

Background Jobs now correctly update IDE Progress, ensuring better synchronization between background processing and what users see in the interface in IDE.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article