â– Specification Description
The details registered in the service will be loaded to the memory in the timing that is started from Trigger or ScriptRunner and Thread component.
Therefore, even if you update in the middle of execution, the script will be executed with the details that are loaded already and the details will never change in the middle.
â– Points to be noted
As described in the specification description, when you call the service using [Call Script] in the middle of thread component, the latest service is loaded at the moment of thread starting.
Hence, only if you call the service using [Call Script] in the middle of thread component, that service will be in the state of thread starting point and not in the script starting point.
For example, let us assume that the below 2 scripts are there in the same service.
Call the child script using [Call Script] in the middle of thread component
Implement the linking process
In such case, when you execute the parent script and re-register the service prior to the thread starting, though the parent script part will be executed in the state (before re-registration) of script starting point, the child script part will be executed in the state (after re-registration) of thread starting point.
Hence, when you call the service using [Call Script] in the middle of thread component, though the details in each script are not changed, the versions executed in parent and child script will differ.