Forge deploy & Forge tunnel KO / time out

Forge Forge Platform and Tools
,
1

Hi all,

Since approx. 13:10 CET, forge deploy & forge tunnel are KO on my side, after Forge CLI update to latest version. API Token renewal does not help. Atlassian Developer Status shows all-green status…

Anyone else experiencing this?

Cheers,

F.

2

I am unable to deploy right now.
grafik

1 Like
3

We are also unable to use Forge now. I guess it is some global/Forge problem right now.

1 Like
4

Forge-tunnel working again, forge deploy KO.

F.

5

forge deploy is still not working, but it is getting further ;D

6

Same here, I wasn’t able to deploy / tunnel in the past 20 min or so

◀️  GraphQL
Request ID: d6223fe3-77e0-4f9e-b714-8e241b040782
Result: {
  "me": {
    "user": {
      "name": "<name>",
      "accountStatus": "active",
      "accountId": "712020:32aa50ef-9952-40f4-b586-c69149879d15"
    }
  }
}

Error: The underlying service call timed out (requestId: 8d3ab93c-c146-4b7c-a288-f4950417921e)

Error: The underlying service call timed out (requestId: 8d3ab93c-c146-4b7c-a288-f4950417921e)
    at MinimalGraphQLRunner.rawRequestWithoutClientError (/Users/<name>/.nvm/versions/node/v20.18.3/lib/node_modules/@forge/cli/node_modules/@forge/cli-shared/out/graphql/minimal-graphql-runner.js:109:27)
7

It’s affecting mostly the users having free trials :slight_smile: as mentioned in the doc

1 Like
8

Hi there,

We are currently experiencing partial unavailability in managing Forge apps on different Atlassian platforms.

Such as apps lifecycle (installation, removals), developer console usage (including tunnelling), and the creation and deployment of Forge apps.

Our team is working diligently to resolve this issue and restore services quickly. We are in the process of identifying the root cause and implementing the necessary fixes.

You can follow the progress of the incident here: Atlassian Developer Status - Management of Apps is partially unavailable on different platforms

Thank you

7 Likes
9

Hi all,

The incident has been resolved now and the service is operating normally now. The incident was unrelated to the changes shipped in the latest version of Forge CLI so please continue using it.

cheers,
AJ

2 Likes