Session ID (“sessionid”) is different every time you run an installable cloud app. Obviously, since the execution of the recorded script depends upon the session ID returned by the server, it is necessary to catch the proper “sessionid” from the CreateSession server response and then attach it to the subsequent requests. That is, correlating the session ID in the script for successful replay.