migrate-experiments.md

@@ -121,6 +121,13 @@ There are two ways to do it:
 **Before running** the second step of the migration (with the new user), remind to change the **queue** parameter (example CLASS_A to bsc_es) if necessary in the platform.conf file.
 
 
+# Check the runtime
+
+After the migration is done, it is recommended to check the runtime, there might be broken links that should be fixed (it is easily done, since the links will be pointing to a path of the previous user running the experiment, just need to update them to the new group and user).
+
+And in the case of running an OSM experiment, there will be some files that need to be executed by the POST job. The ones that will give issues belong to the POST job for which the SIM has already ran, but the POST is still missing dependencies and will run with the new account. The file will be named like `${EXPID}_osm_post_${CHUNK}.sh` and will be in the runtime folder. It will have some paths set up on its generation pointing to the old group and user that ran the experiment before the migrate.
+
+
 
 # Tests done