Appfire Status · History · Incident #104081
RESOLVEDTime to SLA partially facing problem with reaching `/application-properties` endpoint after CoF migration
Major · Started Jul 17, 2025 · 10:17 AM
Appfire Status · History · Incident #104081
RESOLVEDMajor · Started Jul 17, 2025 · 10:17 AM
Duration
12d 22h 8m
Severity
Major
Detection lead
—
User reports
—
Summary
The incident resolved by Atlassian.
Started
Jul 17, 2025 · 10:17 AM
Resolved
Jul 30, 2025 · 8:25 AM
Duration
12d 22h 8m
Severity
Major
Event timeline
Investigating
Jul 17 · 10:17 AM AppfireWe are currently investigating a problem where several instances are facing problems while trying to get the app properties from Jira REST API. No possible reason has been found, we have been able to reproduce it in one of the test environments we have.
Identified
Jul 17 · 12:50 PM AppfireThe problem seems to be the app user not having the correct permission in several instances. We are trying to find possible solutions as well as actions we can take. A ticket to Atlassian has also been submitted.
Identified
Jul 17 · 5:53 PM Appfirehttps://ecosystem.atlassian.net/servicedesk/customer/portal/34/ECOHELP-76209 has been progressed into 'In Progress' status around 4 hours ago, still waiting for further updates.
Identified
Jul 18 · 8:39 AM AppfireAtlassian approved the problem is caused by the Forge and created a incident of their own. https://developer.status.atlassian.com/incidents/8gwd2x0ql9l3 Waiting for fix from Atlassian.
Identified
Jul 30 · 8:25 AM AppfireWe are continuing on waiting a fix from Atlassian.
Resolved
Jul 30 · 8:25 AM AppfireThe incident resolved by Atlassian.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime.
By Designmodo
Designmodo Inc. 169 Madison Ave, #79627, New York, NY 10016, United States
Copyright © 2010-2026. Pulsetic® is a registered trademark.