Skip to content

Invalid Conversation ID #104

@akanshaaa19

Description

@akanshaaa19

Summary

Problem Statement

Invalid conversation ID is being passed in the Glific flow, causing errors in the kaapi backend.

Expected

The user expected that valid conversation IDs would be utilized in the Glific flow without triggering errors.

Actual

Instead, the invalid conversation IDs (@contact.fields.thread_id and @results.questionloop1) are being passed, leading to an error in the kaapi system.

Error Messages

While no specific error messages were provided, it is implied that passing invalid conversation IDs results in a failure within the kaapi backend.

Reproduction Steps

  1. Trigger the Glific flow with an invalid conversation ID (e.g., @contact.fields.thread_id or @results.questionloop1).
  2. Verify that an error occurs in the kaapi backend when the invalid ID is processed.

Additional Notes

The user indicated that they have project_id and timestamp details to track the NGOs, suggesting the potential for support to assist in correcting the flows. References to errors occurred around specific times (5:28 PM and 1:06 PM) and links to Sentry for more examples were shared.

Source

Original message

Hi <@&717982344228896778>
we are getting error in kaapi side when in Glific flow invalid conversation ID is passed
ProjectTech4DevAI/kaapi-backend#916
while this is user error, should support team help those ngos fix their flow? we do have details like project_id and timestamp to track NGO and maybe flow as well.
Want to check this before we suppress this error

Full thread transcript

akhileshnegi: Hi <@&717982344228896778>
we are getting error in kaapi side when in Glific flow invalid conversation ID is passed
ProjectTech4DevAI/kaapi-backend#916
while this is user error, should support team help those ngos fix their flow? we do have details like project_id and timestamp to track NGO and maybe flow as well.
Want to check this before we suppress this error

sangeetamishra._91310: Yes <@727567753246146633> It would be helpful if you share more details so we communicate to those NGOs or discuss internally and take next steps.

akhileshnegi: One such error happened for mukkamaar around 5:28
where conversation id passed was @contact.fields.thread_id

akhileshnegi: another happened for them again around 1:06PM
where conversation id passed was '@results.questionloop1'

akanshaa19: mukkamaar is working on a flow for their pilot. i will help them out with this

akhileshnegi: <@&725604282585317517> you can check here
https://project-tech4dev.sentry.io/issues/7482413437/events/6a119f12f98c4441b7e3615b0945d8c7/?project=4511386692091904
click here to see similar instances for other orgs

akhileshnegi: let me know if anything is needed from kaapi side

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    To Do

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions