# The "act" field in app-context

**URL:** <https://devforum.zoom.us/t/the-act-field-in-app-context/72411>\
**Category:** Zoom Apps\
**Created:** [July 18, 2022, 4:27pm UTC](https://devforum.zoom.us/t/the-act-field-in-app-context/72411 "2022-07-18T16:27:42Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![madhum](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/madhum/32/36087_2.png) [@madhum](https://devforum.zoom.us/u/madhum)\
**Post date:** [July 18, 2022, 4:27pm UTC](https://devforum.zoom.us/t/the-act-field-in-app-context/72411/1 "2022-07-18T16:27:42Z")

</div>

I recently started noticing some strangeness in the “act” param of the app context. Per the documentation, “act” should be the action payload supplied in the deeplink. But I’m seeing some strangeness and was wondering if you can explain some of these:

Normal (we get it all the time):  
act:{}

Strange (as it’s is not a JSON object  
act: ‘go’ → Sometimes

Somewhat Strange (as we never supplied it and it’s coming from somewhere)  
act: { “url”: “/zoomapp/home”, “role\_name”: “Owner”, “verified”:1, “role\_id”: 0}

More Strange (why are we getting codaCode & codaCodeVerifier)  
{“codaCode”: “”, “zoomCode”: “”, “codaCodeVerifier”: “”}

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [July 22, 2022, 11:14pm UTC](https://devforum.zoom.us/t/the-act-field-in-app-context/72411/2 "2022-07-22T23:14:35Z")

</div>

@madhum Can you share the snippet of code you’re using to print this out? I’m not sure why this would be happening off the top of my head.

---

<div class="post-metadata">

**Author:** ![narmadaravali](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/narmadaravali/32/39496_2.png) [@narmadaravali](https://devforum.zoom.us/u/narmadaravali)\
**Post date:** [July 23, 2022, 12:30am UTC](https://devforum.zoom.us/t/the-act-field-in-app-context/72411/3 "2022-07-23T00:30:14Z")

</div>

This happened during the app-context issue. I believe the issue is resolved now.