# "commands" and "participantId" values in grpc ErrorInfo

**URL:** <https://forum.canton.network/t/commands-and-participantid-values-in-grpc-errorinfo/5407>\
**Category:** App Development\
**Tags:** ledger-api\
**Created:** [October 11, 2022, 11:17pm UTC](https://forum.canton.network/t/commands-and-participantid-values-in-grpc-errorinfo/5407 "2022-10-11T23:17:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![huw](https://yyz2.discourse-cdn.com/flex034/user_avatar/forum.canton.network/huw/32/2343_2.png) [@huw](https://forum.canton.network/u/huw)\
**Post date:** [October 11, 2022, 11:17pm UTC](https://forum.canton.network/t/commands-and-participantid-values-in-grpc-errorinfo/5407/1 "2022-10-11T23:17:16Z")

</div>

I have noticed that the `ErrorInfo` for a failed command, contains a “commands” key in its metadata map. See the follow example of it - looks like it is in a JSON format.

```haskell
{readAs: [], deduplicationPeriod: {duration: 'PT1M'}, submittedAt: '2022-10-11T23:04:22.552129Z', ledgerId: 'KVBC', applicationId: 'DLT-Te
st-App', submissionId: '9c0a3adf-9c1b-4670-9653-78ddff1e179e', actAs: ['Alice'], commandId: '81b432a8-4e67-49c8-bb1d-330f81e78509', workflowId: 'd9c4e041-03c0-429c-920e-922fe75b749b'}

```

It also contains a “partipantId”. I have not seen these features documented anywhere. Are they officially supported?