Comment 3 for bug 928933

I confirmed that this happens when the client handles an activity where all the changes have already been performed by other activities or manually.

I guess simply returning a message saying that no changes needed to be done would be good to start with. Later we should check each action to see whether it needs to be executed or not.