Hi ,
I am not getting Forge dev logs since morning… Anybody facing similar issues
1 Like
Hello Ajay,
Our team has not identified any issues on the platform side at the moment. Therefore, for further investigation, we kindly request you to provide us with additional details regarding the app (app IDs if it is specific to few apps).
We are seeing multiple issues with Forge Dev.
I am not getting Forge execution & logs for the below App IDs
940d0b9e-13bb-44ec-8911-65ba027dd04e
cfa65fdd-ab2b-4f2e-a9ad-67b596869122
Regards
Ajay
Another issue being faced by my colleague . Forge install is not working even after deployment
App ID - 6aa0e959-94b9-4235-81df-eed1c3b09242
Thanks for the details. Our team will look into this and we will update you soon.
1 Like
Yes, I am facing the same issue. Unable to see any logs in Dev environment in the console.
2 Likes
I am seeing the same issue with our forge application. No logs from ANY environment in the last ~18 hours or so? I do not see an incident on your status page, but this seems to be an issue for multiple people.
app id: 45fc1408-8ae1-4f55-832c-fc7783b46179
Jira Service Management raised an issue here
Hello Team,
I’m looking into this issue now. When @gdame opened his incident ticket, he also created a public one so you can comment on and watch
for updates. I’ll also update here when I can.
Regards,
James.
I’m also facing the same issue here. Don’t know if this helps, but the last logs I received was from 21st Nov where everything was working fine. I only noticed this issue on the 22nd.
App id: d0dd0f9f-a19d-4775-b413-c106c4facec7
After resolving the current problem, I recommend that the Forge team make the metrics accessible via Forge App Logs. This would greatly aid in differentiating between App issues and Forge Platform issues, as I spent nearly two hours yesterday trying to determine the source of a problem I encountered.
Hi @JeromeRodrigo,
Can you let us know the filters you’ve been using? That is what do you see for Development, Staging and Production and what happens if you go back a month or more?
Thanks,
James.
I just filtered on my personal dev environment with logs filtered to “Last week”. We don’t have logs on development/staging/production because we’ve not deployed there yet. We’re in the early stage of prototyping, so most devs are on their personal environments. I can mention that I had one other colleague who could not view their logs as well recently.
As I write this reply, I just noticed that I now see logs from today 23rd Nov!
Although I don’t see logs from yesterday 22nd Nov.
EDIT: I don’t have logs from a month before, just started working on this app this week.
1 Like
HI Team,
There was an issue between 1.30pm 22/Nov/2023 (UTC+11) and 9:00am 23/Nov/2023 (UTC+11). During this time, any app redeployed that was relying on Sandbox Runtime might have had issues with logs not being properly emitted and therefore not reaching the Developer Console.
For everyone that is affected by this, did you deploy to any of the environments during this window?
As for a fix, please forge deploy to the affected environments to pick up the new runtime so logs will start appearing again.
James.
6 Likes
Yes I deployed during that period. Seeing that I’m getting logs now it should be good now, thanks for keeping us in the loop @jrichards . However it would be nice if any issues were posted to https://developer.status.atlassian.com/ as I didn’t see any incidents regarding this yesterday.
Best regards,
Jerome
1 Like
Redeploying appears to have resolved that for me as well. We also had issues with our oauth login during the same period, though not entirely sure if they were related. Regardless, thanks team for getting on this pretty swiftly.
Hi @JeromeRodrigo,
We don’t always post to status page for incidents, as this was not a high severity issue and was resolved before I started investigating it. The underlying issue was something else and the missing logs was a side effect.
I’ve let a Forge PM know about this to see if there’s a better way to surface messaging that doesn’t warrant a status page.
James.
@jrichards @SamikshaShankarDhabe
I am seeing the issue repeat today for my app on both development & production deployments
App ID -
cfa65fdd-ab2b-4f2e-a9ad-67b596869122
Hi Ajay, acknowledged your concern, allow us some time to check from our end. Hope to provide you an update soon.