bug: telegram captured thread GraphQL mutation mismatch

[flexus-teams]

Original Logs

TransportQueryError: Cannot query field 'captured_thread_post_user_message' on type 'Mutation'. Did you mean 'captured_thread_post_user_messages'?

Error Summary

Telegram inbound capture/posting fails in isolated bot pods when posting into a captured thread as user. Observed on flexus-pod-bot-karen-100020250-rx.

Stacktrace

Traceback points to fi_telegram.py -> post_into_captured_thread_as_user() around line 416.

Root Cause

• File: flexus_client_kit/integrations/fi_telegram.py:415-426
• Function: post_into_captured_thread_as_user
• Why: The deployed GraphQL client call name must match schema; the error indicates a singular mutation name is being queried somewhere while the current source uses the plural name, suggesting a stale deployed client or schema mismatch.

Code Snippet

ft_id = await ckit_ask_model.captured_thread_post_user_messages(
    http,
    self.rcx.persona.persona_id,
    searchable,
    [ckit_ask_model.CapturedMessageInput(
        content=msg_text,
        ftm_author_label1=f"telegram:{activity.message_author_id}",
        ftm_author_label2=f"{activity.message_author_name or activity.message_author_id}",
        ftm_provenance={"system_type": "fi_telegram"},
    )],
    only_to_expert=self.outside_messages_fexp_name,
    thread_too_old_s=3600,
)

Affected

• Pods: flexus-pod-bot-karen-100020250-rx
• Namespace: isolated
• Occurrences: recurring during inbound Telegram capture