I set my agent’s max_call_duration_ms to 3,618,000 (60 minutes) and verified that it was published (version shows is_published: true). However, a call that started AFTER the publish running for 130+ minutes without being terminated. Timeline: Agent version with 60-min limit published: Jan 8 Call started: Jan 9 (after publish) Call duration: 130+ minutes (still ongoing when I checked) Is there a known issue with max_call_duration enforcement? Is there something special about batch calls vs regular calls? I know this may become a billing issue, but I have no way to stop the call now.

hello

Hi

Can you share a call id

call_45ed4a7b83e289a111d83445b84

There an issue happend in this call, it stuck on "ongoing" , it will be turned into error_retell soon , and you will not be charged for it do you have any other calls like this ? or its just this one ?

Only this one. Isn't the max 120 min?

so the call actually is not ongoing but there an issue making it stuck on this status it will automatically turn into error retell.

Ok, is it a 1 - off, or might this happen again?

its rarely happens, if it happend again let me know, and I will escalate it.

Thanks