Hello, in fact the PlugIn "_ComputeOptimalTimeStep" overwrite the timeStep that you put in the header (equal to 1e-5). The "_ComputeOptimalTimeStep" plugin automatically computes the maximal time step that you can put in your simulation. This value depends on the local stiffness and masses of the discrete elements of your simulation.
If you put a time step larger than the value given by the "_ComputeOptimalTimeStep" plugin your simulation may diverge. It is probably the case when GranOO says to you "The problem was detected...saving domain and place element in inconsistent..."
You can easily document yourself about this timestep problem. This is a common and well known problem in DEM and numerical methods.