Process mining dashboard not updating after scheduled data load

BPM Creatio
, , , , , , , ,
1

Running Creatio 8.3.2 in cloud environment. Our process mining dashboard shows stale data even though the ETL job completes successfully every night at 2 AM. The scheduled data load runs without errors (verified in job logs), but the dashboard doesn’t reflect the new data until we manually trigger a refresh through the UI.

We’ve configured the ETL job to load process event data from our ERP system into Creatio’s process mining tables. The job scheduler shows successful completion:


[02:15:33] ETL Job 'ProcessEventSync' completed
Status: Success | Records processed: 15,847
Next run: 2025-01-09 02:00:00

But when users access the dashboard at 8 AM, they see yesterday’s metrics. Only after clicking the manual refresh button does the data update. This defeats the purpose of automated reporting. Has anyone solved dashboard refresh triggers after ETL completion?

2

Alternative approach: use webhooks instead of embedded scripts. Configure your ETL job to POST to a webhook endpoint when it completes. The webhook handler can then orchestrate the refresh sequence (recalculate metrics, clear cache, trigger dashboard reload). This decouples the ETL job from the dashboard refresh logic and makes it easier to add other post-load actions later without modifying the ETL process itself.

3

Configure it in the Process Designer. Add a Script Task element at the end of your ETL process flow. In the script, you need to call both: first RecalculateMetrics() to update the aggregation views, then InvalidateDashboardCache() to clear the cached dashboard data. The two operations are independent - recalculating metrics updates the database views, but doesn’t automatically clear the dashboard’s in-memory cache.

4

The dashboard cache isn’t automatically invalidated when background ETL jobs complete. You need to explicitly trigger a dashboard refresh. Check if your ETL job has a post-completion webhook configured to call the dashboard refresh API endpoint. Without this, the dashboard serves cached data until manual refresh or cache expiration (usually 4 hours).