Forge App Running Outdated Code

We’re running into an interesting/odd issue where the Developer Console is reporting our customers have upgraded to the most recently deployed version of our app (a minor upgrade). However, we’re still see the old version of the code running. In particular, we made changes to information in some of our log messages. We’re not seeing the new messages. Only, the old messages.

I’m very confused by this because everything we can see indicates that ALL of our customers have been updated. Yet, we’re still seeing outdated code.

Is this a known issue? Are there known delays?

I just noticed that there’s a difference between staging and production deploy. “Snapshotting functions” is missing from the production deploy.

Staging

(base) ➜  jira-forge-app git:(main) ✗ forge deploy -e staging                                                                                                                                                                                                                     

Warning: Your version of Forge CLI is out of date. We recommend you update to the latest version to get the latest features and bug fixes.
Run npm install -g @forge/cli@latest to update from version 11.3.0 to 11.3.1.

Deploying your app to the staging environment.
Press Ctrl+C to cancel.

Running forge lint...
No issues found.

✔ Deploying [redacted name] to staging...

ℹ Packaging app files
ℹ Uploading app
ℹ Validating manifest
ℹ Snapshotting functions
ℹ Deploying to environment

✔ Deployed

Deployed [redacted name] to the staging environment.

ℹ The version of your app [4.6.0] that was just deployed to [staging] is not eligible for the Runs on Atlassian program. Run forge eligibility to know more.

To know more about Runs on Atlassian, go to https://go.atlassian.com/runs-on-atlassian

Production

(base) ➜  jira-forge-app git:(main) ✗ forge deploy -e production                                                                                                                                                                                                                  

Warning: Your version of Forge CLI is out of date. We recommend you update to the latest version to get the latest features and bug fixes.
Run npm install -g @forge/cli@latest to update from version 11.3.0 to 11.3.1.

Deploying your app to the production environment.
Press Ctrl+C to cancel.

Running forge lint...
No issues found.

✔ Deploying [redacted name] to production...

ℹ Packaging app files
ℹ Uploading app
ℹ Validating manifest
ℹ Deploying to environment

✔ Deployed

Deployed [redacted name] to the production environment.

ℹ The version of your app [2.8.0] that was just deployed to [production] is not eligible for the Runs on Atlassian program. Run forge eligibility to know more.

To know more about Runs on Atlassian, go to https://go.atlassian.com/runs-on-atlassian

Hi Wesley,

Versions are different per environment deployed.

Regarding your first point raised, that is concerning. Can you please raise a Support ticket so you can share more details with our Forge Engineers.

You can raise it here: Jira Service Management

Cheers
Ben

Hello yes no it has no been updated this is because I have been unable able to. Properly log into my accounts that originally belonged with my atlassin acct I am so sorry you are confused by this but i haven’t had much support when I first reached out to atlassin can I please set up a meeting on Google meet to discuss this matter thank you …

@WesleyHarding Is your app listed on Marketplace? I’ve seen Marketplace stopped auto-publishing the latest Forge App version as public today (5/1/2025). There are new versions created in Marketplace but they stay as private until being make public manually.

The developer console does show that the customer installations are on the latest version. Unfortunately I wasn’t able to verify which version it actually was before I manually made the latest version public.

I do have a screenshot of a reminder about the private version on top of the app listing from the vendor’s view:

Yep, versions are different. That makes sense to me.

This ended up resolving itself, but I’m not really sure why. It seems like roughly 2 to 4 hours after the deploy, the new code started running.

I’m not shocked that there’s some delay, but hours is rather surprising.

1 Like

Sounds like caching.