Where Does Flowdock Store Sessions and Cache?
Where the Flowdock desktop app keeps team sessions and cache on Windows and macOS machines today (details below).
Last updated
Flowdock desktop runs on Electron with a familiar footprint. Sessions, team choice, and flow cache live in a Flowdock folder under AppData Roaming on Windows and Application Support on Mac. Logs sit beside them.
Server data is the backup. Local wipes cost login and drafts, not flows. For new machines just install and sign in. Folder transplants between PCs often carry stale tokens that fail at launch, so fresh login beats copying for this app. Cache clears fix most launch loops without touching teams.
Where Flowdock stores this, by platform
%appdata%\Flowdock
Sessions and flow cache live here. Clear Cache folders to stay signed in. Delete the whole folder closed for a clean logout and fresh sync.
~/Library/Application Support/Flowdock
Same Electron layout under Application Support. Finder hides Library, so use Go to Folder. Logs beside sessions help trace call setup failures.
Frequently asked questions
How do I reset Flowdock when it loops on launch?
Delete the Flowdock folder under Roaming (Windows) or Application Support (Mac) with the app closed, then sign in again. Teams and history return from the server. Only unsent drafts vanish, since they never left local storage.
Can I clear Flowdock cache but stay signed in?
Yes, in Cache and Local Storage under the same roots. Clearing them drops avatars and thumbnails while keeping login. A full folder delete logs out. Either way, flows and history reload on sign in because the server holds the record.
Notice an outdated path? Let us know.