Updating multiple call-to-tests in a test cycle not all updated

Hi all,

We have some behaviour we cannot explain when working with call-to-test. This is the case:

1. Our test script A consists of "normal" steps and several call-to-test steps (more than 10).
2. Test script is added to a test cycle. So far, test works fine.
3. Multiple changes are made to test scripts that are "call-to-test" steps in test script A.
4. In Test Player a message is shown to update the script, because of the multiple changes.
5. The update script message keeps coming back, no matter how often the update button is clicked. (It seems like this behaviour doesn't apply when it is only 1 or 2 call-to-test steps. When it is reasonably more, problems seem to appear.)
6. The status of the call-to-test steps stays "outdated", no matter how often the update button is clicked.
7. The work-around so far seems to be removing test script A from the cycle, and add it again, thus losing the already executed steps and results.

Our questions:

1. Do more users experience the above outlined behaviour?
2. Is there a max to the amount of call-to-test steps in a single test script?
3. Is this a bug?

Any suggestions highly appreciated. Thanks in advance.

Cheers, Erwin