[keria] ERROR eventing .processEscrowA- 2140 Tevery ANC unescrow failed

[shanfeng9001]

We have established a lab environment and a production environment.
Currently, during functional verification in the lab environment, we seem to encounter an issue when creating a Registry. This problem prevents us from querying the Registry record after its creation.

The operation steps in our lab environment are as follows:
Created two AIDs (AID-A and AID-B) using the passcode.
AID-A and AID-B performed the "add contact" operation with each other.
AID-A created a Multisig Group, and AID-B joined this Multisig Group.
AID-A and AID-B each executed the "add Enrole" operation, and the MultiSig AID successfully obtained the oobi URL.
AID-A and AID-B respectively performed the Create operation using the same Registry Name and nonce, but an error occurred.

From the Keria console logs, the same error message is continuously output:
[keria] ERROR eventing .processEscrowA- 2140 Tevery ANC unescrow failed: ANC Missing escrowed anchor at dig = EJoWMc8Jmb9Jr4nUsNCDF0NZw6BCdR4TPR1fx8BiPeKA

The above error can be stably reproduced every time. Meanwhile, the multisig groups we created a few months ago can create Registries normally.
Could you please inform us of the ways to troubleshoot this issue? We believe that simply rebuilding the environment may resolve it, but we hope to find a fix while retaining the original test environment.

The relevant code libraries and their versions relied on by the lab environment are listed below:
signify-ts: 0.3.0-rc1
gleif/keria: 0.3.0
gleif/keri: 1.2.8-rc2

[iFergal]

Hey @shanfeng9001 I tried to reproduce this and couldn't - perhaps you can share a gist or similar of your steps?

Created two AIDs (AID-A and AID-B) using the passcode.

Replying, I just noticed this more closely. Do you mean both AIDs are created using the same Signify client?

[shanfeng9001]

Hey @shanfeng9001 I tried to reproduce this and couldn't - perhaps you can share a gist or similar of your steps?

Created two AIDs (AID-A and AID-B) using the passcode.

Replying, I just noticed this more closely. Do you mean both AIDs are created using the same Signify client?

AID-A and AID-B use different passcodes.

The two AIDs are independent and use different SignifyClient objects.

After AID-A and AID-B completed the necessary steps, an error occurred during Registry creation (duplicate Registry name).

[iFergal]

I used the versions you provided and it worked for me, so likely there is some small error somewhere in how it's being called. Please provide a snippet of the Signify code which reproduces the error!

[shanfeng9001]

Hey @iFergal

With the same code and identical operational procedures, the multi-signature group we created several months ago can successfully set up the registration center.
We have also conducted multiple tests in this lab environment previously, all of which yielded successful results.
However, in the latest tests, we observed that the creation operation fails on the same day but succeeds when re-executed the next day.
We suspect that clearing the data and rebuilding the service will resolve this issue, but we aim to identify the specific root cause of the problem.
Code snippet:

const client = await getOrCreateClient(props.passcode)
const self = await client.identifiers().get(props.prefix)
const ms = await client.identifiers().get(msAlias)

const resp = await createRegistryMultisig(
client,
self,
ms,
regName,
nonce
);

thx

[iFergal]

@shanfeng9001 createRegistryMultisig from the test utils in Signify accepts other arguments to handle the sending of the /multisig/vcp exchange message to the other participants. It contains the anchoring event and gets parsed, so this might be missing judging by your escrow error that outputs continuously. Each participant must collect enough signatures on an anchoring event before it's sent to witnesses.

Are you sending this exn message? (And does the escrow error output stop after a bit or continue? Even in the positive case you will probably see these messages in debug mode because things can arrive out of order.)

Unsure why it would be intermittent though, but it's hard for me to tell right now given I can only see a small snippet. (Is the signing threshold always the same for each group?)

[shanfeng9001]

@iFergal Thank you for your attention and reply.

We understand that this issue is not related to code or logic, as the system ran stably before the problem occurred.

The focus of attention may lie with Keria, and the feedback is as follows:

1. Creation can be successfully completed using previous accounts, but for relatively new existing accounts, Registry creation fails after running for a period of time.
2. The problem occurs during the Registry creation phase (before this, the multi-signature group has been successfully created). If we try again after an interval, it may succeed, but success is not guaranteed.

The relevant service components are as follows:
signify-ts: 0.3.0-rc1
gleif/keria: 0.3.0
gleif/keri: 1.2.8-rc2

[iFergal]

@shanfeng9001 It's hard for me to diagnose further without deeper logs or a longer code snippet. Can you confirm that the /multisig/vcp message is being passed around?

[shanfeng9001]

@iFergal

After multiple rounds of testing and verification, the issue persists. Below is a summary of the relevant background information, along with a request for assistance in resolving the problem:

The system is built on signify-ts and utilizes a KERIA agent.
When using an older account (registered ~6 months ago) and following the exact same steps, the issue does not occur—i.e., after creating a multisig group, the Registry creation succeeds.
Current main test steps (please verify whether this workflow is complete or if any critical steps are missing):
A. Create two independent AIDs, representing two applicants.
B. The two applicants mutually add each other to their contact lists.
C. Create a multisig group: the second applicant executes join, followed by both parties executing add enroll; at this point, both applicants confirm that the multisig group’s OOBI has been successfully created.
D. Both parties attempt to create a Registry—this step fails, and accessing the multisig group’s OOBI returns a 404 error.

We kindly request your guidance on diagnosing and resolving this issue.

[shanfeng9001]

Additionally, here is supplementary information:
When creating the Registry, the createRegistryMultisig function from multisig-utils.ts was used. The core code segment of this function is as follows:

const recp = await listOtherMemberAids(client, ms.prefix, aid.prefix)

await client
.exchanges()
.send(
aid.name,
'registry',
aid,
'/multisig/vcp',
{ gid: ms.prefix },
regbeds,
recp
);

The parameters passed to the send function appear to be valid, with no null or empty values. In particular, the value of the regbeds parameter is:

The return value after executing the send function is:

'{"v":"KERI10JSON0003dd_","t":"exn","d":"EBfirnC1bimJouG33eLN0SeMh48mC7szbbDjuM_uwSvs","i":"EM7NbuDvY_E0Ryzlmf_WOR0fB3dE2M_rhbUbOiKk_k_D","rp":"EPbskY1RwlTPGmTLdHIXnc-rrn5uKt9Z3AHcbUQ2kDOv","p":"","dt":"2026-01-08T02:15:40.010000+00:00","r":"/multisig/vcp","q":{},"a":{"i":"EPbskY1RwlTPGmTLdHIXnc-rrn5uKt9Z3AHcbUQ2kDOv","gid":"EPSLh-cnqtMmaRXuiefEudmoeruRqD1kM_rlXPDAQg9V"},"e":{"vcp":{"v":"KERI10JSON0000e7_","t":"vcp","d":"EFpsJRRxV_ZmDBrMyp8Kk7eyowzHbqrjAY6uw_jJLCrY","i":"EFpsJRRxV_ZmDBrMyp8Kk7eyowzHbqrjAY6uw_jJLCrY","ii":"EPSLh-cnqtMmaRXuiefEudmoeruRqD1kM_rlXPDAQg9V","s":"0","c":["NB"],"bt":"0","b":[],"n":""},"anc":{"v":"KERI10JSON00013a_","t":"ixn","d":"EIWo5ikTo8vNa33JDY2jIXN0bGFeI26GDYhtJ9Oguclm","i":"EPSLh-cnqtMmaRXuiefEudmoeruRqD1kM_rlXPDAQg9V","s":"2","p":"EM59B3a05VPO8_9CKsPkOhEEYcwvaEMfMMrh75uYUX1H","a":[{"i":"EFpsJRRxV_ZmDBrMyp8Kk7eyowzHbqrjAY6uw_jJLCrY","s":"0","d":"EFpsJRRxV_ZmDBrMyp8Kk7eyowzHbqrjAY6uw_jJLCrY"}]},"d":"EP7cg29TQmGU8-ObWA9rAOL5uBIWx4jPveTLMXWu52Y-"}}'

So，What potential causes could lead to a 404 error when accessing the OOBI URL of a newly created multisig group?