UNKNOWN_INFORMEES","cause"

Hello,
Recently, I deployed Testnet node using docker-compose approach, setting the Auth0, configure DA Utility UI. However, when I try to Request Provider Service from UI I got this error:

UNKNOWN_INFORMEES","cause":"The participant is not connected to any synchronizer where the given informees are known.

Any hints is appreciated.

Hi @wshbair , kindly refer on this link for the error code description: UNKNOWN_INFORMEES.

Thanks for the link,
Still how I can Check the list of submitted informees?

Think of “informees” as who got told about your transaction.
After you submit a command and get its transaction ID, fetch that transaction’s tree from the Ledger API; every event in the tree lists the witness_parties (who saw that event). Just collect all the witness_parties from all events and take the unique set, that’s your list of informees.

This is my command

{
  "commands": [
    {
      "CreateCommand": {
        "templateId": "#utility-registry-app-v0:Utility.Registry.App.V0.Service.Provider:ProviderServiceRequest",
        "createArguments": {
          "operator": "auth0_007c65f857f1c3d599cb6df73775::1220d2d732d042c281cee80f483ab80f3cbaa4782860ed5f4dc228ab03dedd2ee8f9",
          "provider": "VNXCommoditiesAG-testnet-3::1220ffef2f552098e0570493480059f7eaa94e3929246417a5d0899e709105e8eeb5"
        }
      }
    }
  ],
  "workflowId": "",
  "userId": "auth0|6932d2a93f61a0098ab2667f",
  "commandId": "842f74c27ac845cd01490b3e8904c49545b22ee5",
  "deduplicationPeriod": {
    "DeduplicationDuration": {
      "value": {
        "seconds": 30,
        "nanos": 0
      }
    }
  },
  "actAs": [
    "VNXCommoditiesAG-testnet-3::1220ffef2f552098e0570493480059f7eaa94e3929246417a5d0899e709105e8eeb5"
  ],
  "readAs": [],
  "submissionId": "e410497b-fc85-47b7-9794-0725711dbe03",
  "disclosedContracts": [],
  "domainId": "",
  "packageIdSelectionPreference": []
}

This is the response I got:

{

"code": "UNKNOWN_INFORMEES",
"cause": "The participant is not connected to any synchronizer where the given informees are known.",
"correlationId": null,
"traceId": "29f6ec358ac7699027d019a619e9428e",
"context": {
"participant": "participant",
"unknownInformees": "Set(auth0_007c65f857f1c3d599cb6df73775::1220d2d732d042c281cee80f483ab80f3cbaa4782860ed5f4dc228ab03dedd2ee8f9)",
"category": "11",
"tid": "29f6ec358ac7699027d019a619e9428e",
"definite_answer": "false"
    },
"resources": [],
"errorCategory": 11,
"grpcCodeValue": 5,
"retryInfo": null,
"definiteAnswer": null
}

looks like the operator is not know, but how to fix ?

You’re hitting UNKNOWN_INFORMEES because the participant you’re submitting to isn’t connected to any synchronizer (domain) where one of the stakeholders/observers of the new contract, here, operator = auth0_007c65…::1220d2d7…, is known. For a Create, the informees are the signatories and observers of the created contract; every informee must be known on (i.e., allocated/hosted or at least discoverable via topology on) some synchronizer the submitting participant is connected to.

So how i can fix this ?

Use ListKnownParties/GetParties on that participant to confirm both the actAs provider and the operator are listed; if the operator is missing, either allocate/import it on this participant’s synchronizer or connect this participant to the synchronizer that hosts the operator and ensure hosting/topology is published.

Thanks for your hint, it really help
I found the given operator exist in the Devnet while my node run on Testnet. So I changed the the config as follows:
UTILITY_APP_UTILITY_BACKEND_URL="``https://api.utilities.digitalasset-staging.com``"

You’re welcome. If there would be additional questions/concerns, feel free to reach out. Happy to help.