# Forge remote context is empty when invoked from rovo

**URL:** <https://community.developer.atlassian.com/t/forge-remote-context-is-empty-when-invoked-from-rovo/91063>\
**Category:** Rovo\
**Tags:** forge-remote, rovo-agent\
**Created:** [April 10, 2025, 7:43am UTC](https://community.developer.atlassian.com/t/forge-remote-context-is-empty-when-invoked-from-rovo/91063 "2025-04-10T07:43:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![skv040391](https://avatars.discourse-cdn.com/v4/letter/s/839c29/32.png) [@skv040391](https://community.developer.atlassian.com/u/skv040391)\
**Post date:** [April 10, 2025, 7:43am UTC](https://community.developer.atlassian.com/t/forge-remote-context-is-empty-when-invoked-from-rovo/91063/1 "2025-04-10T07:43:40Z")

</div>

I’m building a rovo agent for connect app.

Here is how I defined action

```auto
 action:
    - key: start-timer
      name: Start timer
      endpoint: startTimer
      actionVerb: GET
      description: >
        When a user asks to start a timer, this action starts a timer for the issue
      inputs:
        issue:
          title: Issue
          type: string
          required: true
          description: |
            "Issue key for which user has requested timer to start"
  endpoint:
    - key: startTimer
      remote: connect
      route:
        path: /rovo_actions/start_timer
      auth:
        appUserToken:
          enabled: true
        appSystemToken:
          enabled: true

```

In the endpoint I successfully verifed JWT token but context is missing **siteURL**.

According to the documentation it should be there

> **[Forge remote essentials](https://developer.atlassian.com/platform/forge/remote/essentials/#the-forge-invocation-token--fit-)**
>
> The key considerations and responsibilities of using Forge remote.

in the context I have only `cloudId` an `moduleKey`

Did I miss something or is it intentional?

---

<div class="post-metadata">

**Author:** ![dmorrow](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/dmorrow/32/35895_2.png) [@dmorrow](https://community.developer.atlassian.com/u/dmorrow)\
**Post date:** [April 14, 2025, 9:11pm UTC](https://community.developer.atlassian.com/t/forge-remote-context-is-empty-when-invoked-from-rovo/91063/2 "2025-04-14T21:11:23Z")

</div>

Hi @skv040391 ,

Welcome to the Atlassian Developer Community.

This seems like a bug so could you raise a support case [here](https://ecosystem.atlassian.net/servicedesk/customer/portal/34/group/3534/create/4180) please. The support team should be able to help you get to the bottom of the problem.

Regards,  
Dugald

---

<div class="post-metadata">

**Author:** ![YY1](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/yy1/32/47408_2.png) [@YY1](https://community.developer.atlassian.com/u/YY1)\
**Post date:** [April 15, 2025, 5:54am UTC](https://community.developer.atlassian.com/t/forge-remote-context-is-empty-when-invoked-from-rovo/91063/3 "2025-04-15T05:54:40Z")

</div>

> [@skv040391](#):
>
> In the endpoint I successfully verifed JWT token but context is missing **siteURL**.

I guess they’re the same bugs and Atlassian developers are working on it. [context:siteURL has been removed recently. Please add it back](https://community.developer.atlassian.com/t/context-siteurl-has-been-removed-recently-please-add-it-back/91111)