"Log call" during an active call takes ~12 s before the form opens (fast after hang-up)
We use App Connect - BETA - Release Candidate 2.1.4 (Chrome on macOS) with our own private connector, built on @app-connect/core 2.0.0. On an inbound RingEX call, clicking Log call while the call is still connected shows a spinner for about 12 seconds before the log form opens. After hang-up, Log call on the same call opens the form in about a second.
What we measured on Nov 5, 2026 (our connector server's request log, UTC):
- 09:12:06 the call was answered. App Connect's lookup requests reached our server; the slowest took 0.8 s.
- 09:12:23 we clicked the caller (GET /open, our marker), then clicked Log call at once.
- 09:12:34 the next request (GET /callLog) reached our server and was answered in 66 ms. The form opened right after.
- Between the click and 09:12:34, no request reached our server. Earlier tests on 2.1.3 (Oct 28, 2026) showed the same pattern.
What we see in the extension code: on an active call, isCallDataComplete() is false, so the log handler calls RCAdapter.getCallLog({ sessionId }) (/get-call-log). That request can wait up to its 3 s postMessage timeout. For an in-progress RingEX call the widget's call logger has no record yet, so it also tries the RingCX getCall fallback. That explains up to about 3 s, not 12.
Questions:
- Is a ~12 s wait expected when logging during a live call?
- Can the manual log form on an active call skip the record recovery and open with the live call data?
- Is there a setting that shortens it?