Ensemble Manager does not detect Model Configuration updates from Model Catalog

[mosoriob]

Problem Description

The Ensemble Manager does not automatically detect when Model Configurations are updated in the Model Catalog. This creates a synchronization issue between the two systems.

User Scenario

Consider user William who:

1. Created a ModelConfiguration on the Model Catalog using his Tapis App
2. Ran executions using the Ensemble Manager with this configuration
3. A few days later, discovered a bug in the Tapis App
4. Created a new version of the Tapis App and updated it in the Model Catalog
5. Modified the Model Catalog Configuration or Configuration Setup

Current Issue: The Ensemble Manager continues to use the old Model Configuration data and doesn't reflect the updates made in the Model Catalog.

Impact

• Executions may run with outdated or buggy model configurations
• Users cannot easily propagate model updates to existing ensemble workflows
• Manual intervention is required to synchronize changes between systems

Current Workaround

To manually update the Model Configuration in the Ensemble Manager:

1. Access the Hasura database interface
2. Navigate to the "Data" tab
3. Select the "Model" table
4. Find and select the row corresponding to the affected model
5. Edit the model configuration data directly in the database

Suggested Solution

The Ensemble Manager should implement a mechanism to:

• Periodically check for updates to Model Configurations in the Model Catalog
• Provide an API endpoint to manually trigger synchronization
• Automatically detect configuration changes before execution runs
• Log when configurations are updated for audit purposes

Labels

• bug
• enhancement
• model-catalog
• synchronization