Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Communication b/w AI Engine and Agent is Getting Stuck at Queue Envelope #16

Open
2 tasks done
neerajkrbansal1996 opened this issue Jul 4, 2024 · 5 comments
Open
2 tasks done
Assignees
Labels
c-bug Category: Something isn't working p-critical Priority: Critical priority task s-confirmed Status: This is a confirmed issue

Comments

@neerajkrbansal1996
Copy link

neerajkrbansal1996 commented Jul 4, 2024

Prerequisites

  • I checked the documentation and found no answer to my problem
  • I checked the existing issues and made sure there are no similar bug reports

Category

Bug in Agentverse

Expected Behavior

No response

Observed Behavior

Getting stuck at the Queue Envelope

image

The same agent is running fine when running locally.

To Reproduce

No response

Environment Details (Optional)

Agent Address: agent1qtq489yn4qc4ljmqztxtcwsq774u456p8005jyr8738kdah5mla2csn7q7d
Session ID: 133e9cc0-f1ff-40bf-8b81-e403bb7b168a
AV/AI Engine Enviornment: Production

Failure Logs (Optional)

No response

Additional Information (Optional)

No response

@lrahmani lrahmani added c-bug Category: Something isn't working p-high Priority: High priority task labels Jul 5, 2024
@lrahmani lrahmani assigned lrahmani and unassigned jrriehl Jul 5, 2024
@lrahmani lrahmani added p-critical Priority: Critical priority task and removed p-high Priority: High priority task labels Jul 9, 2024
@neerajkrbansal1996
Copy link
Author

I have tried running the same agent in the Local Environment, it is working fine, so it seems like a issue in the AV.

@lrahmani lrahmani added the s-confirmed Status: This is a confirmed issue label Jul 12, 2024
@lrahmani
Copy link
Collaborator

@neerajkrbansal1996 Issue identified, currently working on a fix

@jrriehl
Copy link

jrriehl commented Jul 19, 2024

We have implemented some retry logic on the messages now. Can you please try again @neerajkrbansal1996 and let us know if this is still occurring? We will also be rolling out some updates to improve DB performance next week so that hopefully the retries won't be needed.

@neerajkrbansal1996
Copy link
Author

We have implemented some retry logic on the messages now. Can you please try again @neerajkrbansal1996 and let us know if this is still occurring? We will also be rolling out some updates to improve DB performance next week so that hopefully the retries won't be needed.

it is working now, there is one instance where it failed, it maybe due to fact you mentioned about retry logic, but worked next couple of times i tried. I will let you know if the issue arises again!

@kshipra-fetch
Copy link
Collaborator

Hi @neerajkrbansal1996

Can you please confirm if this is working fine for you now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c-bug Category: Something isn't working p-critical Priority: Critical priority task s-confirmed Status: This is a confirmed issue
Projects
None yet
Development

No branches or pull requests

5 participants