You're right yes 👍 , and this is precisely what I do 😁 . But when trying to access the fourth "page" with scroll_id returned on the third "page" I get above error and I am not able to access data on that fourth "page". This seems to be systematic: Using the scroll_id of the penultimate "page" doesn't allow to access to the very last "page" 🤔 .

I debugged using my browser and following URLs (based on the scheme "api_server" + "/events.get_task_events" + "?task=" + "<my-ta...

Yes, this is that indeed 😉 , to be able to freely choose the a-axis title depending on whether we intend to log data according to iterations or epochs 😃 .

Hi @<1523701205467926528:profile|AgitatedDove14> ,
Thanks again for your insight.
I see how to retrieve the URLs via " POST /events.get_task_events ".
However, regarding your recommendation of using StorageManager class to delete the URL, it seems that this class only contains methods for checking existence of files, downloading files and uploading files, but no method for actually deleting files b...

Okay thank you for your snippet @<1523701205467926528:profile|AgitatedDove14> 🙏 , I will investigate this class! 😉 👍

Hi @<1523701205467926528:profile|AgitatedDove14> , this is it yes!
A solution for freely choosing the x-axis title in the UI depending on the scalar (e.g., as in the screenshot above, but with "Epochs" instead of "Iterations" for the plot on the left 😉 ).
Do you think such a feature exists in ClearML?

Hi @<1523701205467926528:profile|AgitatedDove14> ,

That was exactly that! Thank you for the hint! ✅ My scalars now get pursued as they should when resuming a training from latest checkpoint! 🤩

Just one more question, do you have any idea about how I could change the x-axis label from "Iterations" to "Epochs" for some specific scalars only? I saw from " [ClearML Doc > CearML Fundamentals > Logger > Types of Logged Results](https://clear.ml/docs/latest/docs/fundamentals...

Yes, I mean in the UI, just for the title of the x-axis.
For instance, in the graphs below, I am reporting "mIoU" metric by epochs . It's ok for "time" for instance to leave the x-axis title as "Iterations", but for "mIoU", I was wondering if it would be possible to change "Iterations" to "Epochs" for clarity 🙄 .
Thank you again for your reactivity and support! 🙏
![image](https://clearml-web-assets.s3.amazonaws.com/scoold/images/TT9ATQXJ5-F06G82XM26B/screenshot_from_2024-02-01_09-08-...

Hi @<1523701205467926528:profile|AgitatedDove14> , that's a very good point!
I found issue " Possibility to choose any scalar for horizontal x-axis #1186 " opened one month ago that is pretty close to what I suggest. I will complement it with my graph screenshots to illustrate the issue!
Thank you for your recommendation 🙇

Thank you! 😁 🙇

Are you saying you see them in the UI, but cannot access them via the API ?

Yes, that's it! As you can see in the video above ⤴ , I can see the remaining images (i.e., the images that haven't been deleted) both in the UI and physically on my disk storage, but cannot access them via the API (their leading URL does not exist).

(this would be strange as the UI is firing the same API requests to the back end)

And yes, this is strange b...

Alright, thank you for your insight @<1523701205467926528:profile|AgitatedDove14> ! I will check this link.
Regarding S3, that's a very good point, but the team I work with currently doesn't want to leverage an external cloud storage provider.

Hello @<1523701205467926528:profile|AgitatedDove14> ,

Good news! It seems that using the list of URLs retrieved via "POST /events.get_task_events" and then deleting the corresponding images using StorageHelper class effectively does the trick! 🏆 FYI, here is the little function I wrote for deleting the files:

    from clearml.storage.helper import StorageHelper
    
    def delete_image_from_clearml_server(image_url: str) -> None:
        storage_helper = StorageHelper.get(url=...

Hi @<1523701205467926528:profile|AgitatedDove14> ,
Thanks a lot for your recommendation, that's exactly that! 🤩
I was able to use the scroll_id of the current "page" to access to events of the next "page"!
This works fine and I can now delete almost all debug samples.
I say "almost" because, apparently, using this technique of the scroll_id systematically does not allow to access to the events of the very last "page"...
In fact, as you can see on the picture below :arrow_headin...