@<1566596960691949568:profile|UpsetWalrus59> - please note that if you report the plots as two separate series of the same metric - it should work better

Great, thanks!

Thank you @<1566596960691949568:profile|UpsetWalrus59> for sharing these steps , we were able to reproduce on our end and working on a fix

Hi @<1566596960691949568:profile|UpsetWalrus59>
Could it be the two experiments have the exact name ?
(I sounds like a bug in the UI, but I'm trying to make sure, and also understand how to reproduce)
What's your clearml-server version ?

Response:

I came up with this minimal example - it is a bit different but the behavior is also not as expected I think:

import numpy as np
import plotly.express as px
from clearml import Task

task = Task.init(project_name='MyProject', task_name='task1', 
                 task_type=Task.TaskTypes.training)
logger = task.get_logger()
y_pred = np.random.rand(100)
y_test = np.random.rand(100)
fig = px.line({'y_pred': y_pred, 'y_test': y_test})
logger.report_plotly(title=f'Forecast', series=f'Forecast', iteration=0, figure=fig)

I executed this code twice with just changing the task_name to 'task2'.
Server version is WebApp: 3.17.1-1039

@<1566596960691949568:profile|UpsetWalrus59> - if you could also paste the payload and response of the call to events.get_multi_task_plots - from the network tab of the browser's dev-tools (F12), this might also help understand

Request payload:

{"tasks":["425335514d444646b1077cb8b738ccf7","3c0db63779e940cc80895af728aac5ab"],"model_events":false,"no_scroll":true,"iters":1}