Closed zmezei closed 4 days ago
Issue is due to uagents and delta-v using almanac contract to resolve agents addresses. Hosted agents register first to almanac api and then send the registration request to the contract in a best effort fashion. I increased system resources to expedite contract registration requests and we will update uagents to always resolve addresses from almanac api first
All hosted active/running agents on AV, are showing offline on DV Almanac status is also active but found no endpoints from contract
uagents 0.13 fixes the issue. Ai engine uagents upgrade rolled out to prod now
Prerequisites
Category
Bug in Agentverse
Expected Behavior
Being able to send message to a hosted agent from an agent script or from DeltaV/AI engine.
Observed Behavior
Not being able to send message to a hosted agent from an agent script or from DeltaV/AI engine.
To Reproduce
I tried it multiple times, for example I have a running hosted agent with address agent1qdmtwdg0qnv50mf2s3ntppal5339ms57wnya0xk6ttvt72tq269c6ll82rw.
It doesn't show any error in logs:
but when I try to send message from DeltaV or from a local script it says that it can't resolve endpoint: local script:
log of the running agent:
DeltaV:
As you can see the agent address is the same everywhere.
Environment Details (Optional)
No response
Failure Logs (Optional)
No response
Additional Information (Optional)
No response