bug: telegram captured thread GraphQL mutation mismatch

Open
#336 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
graphql, python
Domain
api, backend

Research direction

Start in flexus_client_kit/integrations/fi_telegram.py around lines 415-426 and inspect post_into_captured_thread_as_user, then trace the generated GraphQL client call and the deployed client or schema involved in the isolated pods. Reproduce the inbound Telegram capture failure and verify that the mutation name used by the deployed pods matches the available schema and posting succeeds.

Written by the indexing model from the issue text.

Description

bug

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
Dominant language
Python
Stars
6
Forks
2
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from smallcloudai/flexus-client-kit

All issues in smallcloudai/flexus-client-kit

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.