I've never had that happen, and I can't see what in the mission could have caused it. It's possible the navigation subsystem was destroyed, but there are sexps that should guard against that. Make another attempt (might as well download the update first, see below) and see if it happens again.
I'm sorry to report I tried it again after doing the update and the problem is still there. The GVC Khitteb moves to the node and when it gets in there it just sits there and never jumps out (I checked its NAV subsystem to see if that had got to 0% but it was healthy. The GTC Pallas jumped out before it but the ISF AWACS ship jumps out after the Khitteb (in fact the AWACS ran into the Khitteb and pushed it forward a little before the AWACS jumped out).
Since the Khitteb doesn't jump out, the Himoltep and Halifax end up not moving toward the node either. I tried jumping out myself to see what would happen, and I got the usual debriefing text and "We have no recommendations for you" but it said I couldn't advance since I failed the mission.
I tried to do a debug build again to get a log but got this now:
Warning: Couldn't find event name "continue campaign" in mission sa_g1_07.fs2.
Returning false for event_status function.
File: sexp.cpp
Line: 13771
ntdll.dll! ZwWaitForSingleObject + 10 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 156 bytes
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_0_x64_SSE2-FASTDBG.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 13 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes
However, this time I was also able to get the mission itself. A log is attached.
I don't know if it will help but I've also attached the mission "Irkalla Passes". Maybe something went wrong with my copy. Better to give you a little too much rather than you say I didn't give you enough info (better safe than sorry) right?
[attachment stolen by Russian hackers]