One of the reasons for this issue could be the names of successively saved data files and any associated intermediate case files from Fluent. Following should be the naming convention (which is obeyed by default from Fluent unless some changes are made in the file names during the solution): Let’s say the first case file is saved with a name sample-1.cas Then the successive data files should have the same name, only appended with time-step/flow-time. sample-1-00.dat sample-1-01.dat … sample-1-50.dat Say after 50 time-steps, some changes are made in the Fluent case file. If this modified case file is not explicitly saved by the user with a new name, the updated case file will be automatically written by Fluent while saving the next data file with the name: sample-2.cas The ensuing data files would then have names like sample-2-51.dat sample-2-52.dat … sample-2-100.dat Such a series of file names would result in automatic loading of all the time-steps in CFD-post, if any one of the case files is selected while loading results. Note that, if sample-2.cas is missing in the above series of data files, the data files from sample-2-51.dat onwards would not be loaded. Then, either rename the data files to have names in the series of sample-1-51.dat, sample-1-52.dat and so on. Alternatively, copy the case file sample-1.cas and rename it to sample-2.cas. Any other names for data files like “sample-1-1-01.dat” or intermediate case files like “sample-2-1.cas” etc. would fail to load all the time-steps in CFD-post for this example.