Where Does PagerDuty Store Incidents and Cache?
Where PagerDuty desktop keeps cache on Windows and macOS, while incidents live in cloud. See the folder table below.
Last updated
PagerDuty is incident cloud with a desktop shell. Your account holds services, on call schedules, and timelines. The computer holds login, preferences, and cached incident views.
Same login means same services. Exact cache names shift with incident versus stakeholder builds. Keep online during swaps so acknowledgements upload. If services vanish, check the account region first. A second trial subdomain is the usual empty schedule cause with on call tools. When in doubt, verify paths inside the app before trusting a remembered folder.
Where PagerDuty stores this, by platform
%appdata%\PagerDuty
Login and timelines live here. Incidents follow your PagerDuty account. Clear cache to fix loads. Match the subdomain exactly on the new machine.
~/Library/Application Support/PagerDuty
Same layout under Application Support with PagerDuty in the name. Services stay in cloud. Use Go to Folder since Library hides.
Frequently asked questions
How do I fix PagerDuty desktop stuck on loading?
Clear the PagerDuty cache folders under Roaming or Application Support, then sign in again. Services, incidents, and schedules live in your PagerDuty cloud account. Only login and cached timelines vanish locally, which rebuild on next open.
Does clearing PagerDuty cache resolve incidents?
No. PagerDuty streams incidents from your account services. The desktop wrapper caches timelines and login. Deleting cache logs out at worst but never resolves an incident. Reopen from the dashboard after clearing and sign back in.
Notice an outdated path? Let us know.