Does anyone understand why the Message History API returns a 504 Gateway Timeout when querying conversations routed through our secondary BYOC trunk during a failover event in the Asia/Singapore region? We have 15 trunks configured, and while the primary trunk reports metrics correctly, the secondary trunk consistently drops the payload after the 30-second timeout threshold, even though the SIP registration remains active and stable.