Run not found

[timpiperseek]

🐛 Bug

When a run has started and you click into the run via the UI. a response is returned "run not found".
I am pretty new to aim but is this expected? Is there a certain amount of time that I should be waiting for?

Expected behavior

loads the run within a couple of seconds of the run starting.

Environment

• Aim Version
  3.29.1
• Python version
  Python 3.9.2
• pip version
  pip 21.3.1
• OS (e.g., Linux)
  -linux
• Any other relevant information
  running on a remote aim server

Additional context

[eagomez2]

Hi,

Did you solve it? I am facing the exact same issue sometimes. For example, when I open the Logs tab of a run, I get this sporadically, but then if I click another tab and come back to the Logs tab I can see my actual logs. My run definitely exists and has data to show, but having to circumvent this behavior every time is a bit problematic.

[jonathanlaib]

I'm facing the exact same issue. Did anyone find a solution/workaround yet?

[eagomez2]

Hi @jonathanlaib ,

It seems that in my case most of the issues were caused by partially loaded data, although it looks a bit confusing to me since I don't know if it is caused by that or by another error. I usually use aim storage reindex and wait a little bit before moving between tabs.

[David2011Hernandez]

Hi @eagomez2 I am facing the same issue and also for me running aim storage reindex solves the issue. One question how did you figure out that the issue might be related to partially loaded data?. Have you found any other clue, I was thinking on a cronjob that nigthly runs aim storage index , but wanted to avoid it if possible