[BUG] MonitorStats.get_pipeline_run_count attempts to read pipelines from other repositories/workspaces
Mage version
0.9.77
Describe the bug
Mage workspaces intermittently emit bursts, often multiple at the same timestamp, of errors indicating that pipelines do not exist in the current repository, even though those pipelines belong to other workspaces and have never existed in the current workspace.
The errors appear to originate from MonitorStats.get_pipeline_run_count, which attempts to retrieve run counts for pipelines that are not present in the current repo_path.
These errors do not appear to impact pipeline execution but generate significant log noise.
To reproduce
No response
Expected behavior
Mage should only attempt to collect pipeline run statistics for pipelines that exist in the current workspace repository.
Screenshots
Operating system
No response
Additional context
We run multiple Mage workspaces in the same environment, each pointing to different repositories. The logs suggest that monitoring logic may not be isolating pipelines per repo?
Source: mage-ai/mage-ai