Support feedback:

When I do a delayed commit, on the Remote Run dialog I check "Commit if
successful" and "with confirmation." The job is submitted and completes
successfully; however, the commit doesn't happen. Instead, TeamCity
creates a new (duplicate) changelist in Perforce with the same
description, and moves my file(s) from the original changelist to the
new one. In the Changes pane, IDEA shows this new changelist as
"Delayed Commit (date and time)."

So for example, I created a changelist (Perforce #318430) with a single
file in it. I submitted it for a delayed commit; it succeeded. Now in
P4Win I see two changelists: #318430 which is now empty, and #318448
which has my single file. IDEA shows both changelists in the Changes
dialog; the first one (318430) is shown with the changelist description
and "(No files) - Perforce #318430", but the second (318448) is titled
"Delayed Commit (Mon Nov 13 09:14:34 PST 2006) (1 file) - Perforce

1. 318448".

Bottom line is that I didn't receive a confirmation, nor did TeamCity
commit the changelist. I'm pretty sure that TeamCity considered the
build to be successful since the TeamCity Quick View (Window tray
utility) shows the build as passing all tests, and I received an email
from TeamCity saying the build succeeded. I would have expected a
confirmation through IDEA (in addition to email) since I checked "with
confirmation", and that confirmation should probably tell me if the
build succeeded or failed.

I can work around this problem by just submitting the delayed commit
manually after the build succeeds.

Issue wasresolved