Hello!
May be the problem is some missing correlation. In SIEBEL it is relevant if you iterate with or witout login. If you iterate without new login some more values have to be regarded as critical. I do not have much expeirience with SIEBEL but in my scripts at least the following was relevant, if the login part was separated from the action part.
SWEBHWND
This may be some unique value. It seems not to be delivered from the server probably it is generated in the browser. It occurs only once in the script at the beginning. It seems to be some session identifier.
It is a seven digit random number.
SWEC
This is the sequence of windows. For this there are two different values. One value remains the same during the complete flow, the other is increased by one on each occurrence in the flow – with a few exceptions.
To compute this value is only necessary if the Init and Action are separated. If login is happening on each iteration this is not required.
If this is done the numbers should be increased in the same pattern than it happened during recording – sometimes the number is not increased.
SWEACn
Between different recordings this value changes. It needs to be correlated at the beginning of the script.
This means:
If there is some missing correlation the script may fail in the second iteration although the fist iteration succeeds - and so some more corelation ends with an error message.
Regards
Thomas