When Tallyfy experiences problems like pages not loading properly, errors appearing, or features not responding correctly, these systematic troubleshooting steps can resolve most issues before requiring support assistance:
Browsers sometimes cache outdated versions of the Tallyfy web application, causing functionality issues. A “hard refresh” forces your browser to bypass cached files and download the most current code directly from Tallyfy’s servers.
To perform a hard refresh, use your browser’s built-in refresh options. Most browsers allow you to right-click the reload button and choose “Empty Cache and Hard Reload” or similar options from the menu that appears.
If a hard refresh doesn’t help, try clearing your full browser cache using the links in step 1 above.
If you’re experiencing authentication loops where the system keeps asking for credentials repeatedly, can’t properly sign in, or get stuck in a redirect cycle, the solution is to force a complete logout to clear all session data.
*.tallyfy.com domainsIf the standard logout URL and cache clearing don’t resolve persistent login or signout issues, you can use this comprehensive script to wipe all Tallyfy-related data from your browser. This removes every trace of cookies, localStorage, sessionStorage, IndexedDB, cache storage, and service workers.
How to use this script:
https://go.tallyfy.comhttps://account.tallyfy.comThe script:
(async () => { const log = (...a) => console.log("[tallyfy-all-origins]", ...a);
// ---- Cookie helpers const cookieNames = document.cookie .split(";") .map(c => c.trim()) .filter(Boolean) .map(c => c.split("=")[0]);
// Build domain candidates: current host chain plus .tallyfy.com (site-wide) const host = location.hostname; // e.g., go.tallyfy.com const parts = host.split("."); const domains = new Set([host, "." + host, ".tallyfy.com"]); for (let i = 1; i < parts.length - 1; i++) { const d = parts.slice(i).join("."); domains.add(d); domains.add("." + d); }
// Build path candidates from deep to root const segs = location.pathname.split("/").filter(Boolean); const paths = new Set(["/"]); let acc = ""; for (const s of segs) { acc += "/" + s; paths.add(acc); } const pathList = Array.from(paths).reverse();
const expire = (name, domain, path) => { const pieces = [ `${encodeURIComponent(name)}=`, "Expires=Thu, 01 Jan 1970 00:00:00 GMT", "Max-Age=0", `Path=${path}` ]; if (domain) pieces.push(`Domain=${domain}`); document.cookie = pieces.join("; "); };
try { log(`Attempting cookie deletions for ${cookieNames.length} visible (non-HttpOnly) cookie(s).`); for (const name of cookieNames) { // host-only attempt for (const p of pathList) expire(name, null, p); // domain/path permutations (incl. .tallyfy.com if applicable) for (const d of domains) for (const p of pathList) expire(name, d, p); } log("Cookie deletion attempts complete (covers host-only & domain-scoped variants where JS-visible)."); } catch (e) { console.warn("[tallyfy-all-origins] cookie error:", e); }
// ---- Web Storage try { localStorage.clear(); sessionStorage.clear(); log("Cleared localStorage & sessionStorage."); } catch (e) { console.warn("[tallyfy-all-origins] storage error:", e); }
// ---- IndexedDB try { if (indexedDB && indexedDB.databases) { const dbs = await indexedDB.databases(); if (Array.isArray(dbs)) { for (const db of dbs) { if (!db?.name) continue; await new Promise(res => { const req = indexedDB.deleteDatabase(db.name); req.onsuccess = req.onerror = req.onblocked = () => res(); }); } } log("Deleted IndexedDB databases for this origin."); } else { log("indexedDB.databases() unsupported here; cannot enumerate DBs."); } } catch (e) { console.warn("[tallyfy-all-origins] indexedDB error:", e); }
// ---- Cache Storage (PWA caches) try { if (self.caches?.keys) { const keys = await caches.keys(); await Promise.all(keys.map(k => caches.delete(k))); log("Cleared Cache Storage for this origin."); } } catch (e) { console.warn("[tallyfy-all-origins] cache error:", e); }
// ---- Service workers try { const regs = (await navigator.serviceWorker?.getRegistrations?.()) || []; await Promise.all(regs.map(r => r.unregister())); log(`Unregistered ${regs.length} service worker(s) for this origin.`); } catch (e) { console.warn("[tallyfy-all-origins] service worker error:", e); }
log("Done on this origin. Repeat on any other Tallyfy origins you use (e.g., go.tallyfy.com, account.tallyfy.com).");})();What this script clears:
.tallyfy.com domainWhy you must run per origin:
Browser security (same-origin policy) prevents JavaScript running on one domain from accessing another domain’s storage. Each Tallyfy subdomain maintains separate storage that can only be cleared when you’re actually visiting that subdomain.
HttpOnly cookies limitation:
HttpOnly cookies are invisible to JavaScript for security reasons. To remove these, use Chrome’s built-in site data manager after running the script:
This removes all site data including HttpOnly cookies across all Tallyfy subdomains.
Tallyfy implements rate limiting to prevent system abuse and ensure platform stability. When you exceed these limits within specific timeframes, you may encounter temporary restriction errors:
| Action | Limit (Approximate) |
|---|---|
| Update Email/Password | 3 times / day |
| Update Account Details | 7 times / day |
| Send/Resend Invites | 10 times / day |
| API Calls | ~140 / 10 secs (can vary) |
| API GET Requests | ~12 / 5 secs (can vary) |
When you encounter rate limit restrictions, wait the specified time period before attempting the action again. If your legitimate use case requires higher limits (such as API integrations), contact our support team to discuss increased allowances.
Sometimes members (especially Light members) experience an issue where attempting to reset their password directs them to create a new account instead. This typically happens when the system doesn’t properly recognize their existing account status.
Follow these specific steps to properly reset your password when experiencing this issue:
Sometimes after successfully logging in or resetting your password, you’re incorrectly redirected to the organization creation page (go.tallyfy.com/organizations/create) instead of your existing organization. This happens when the browser session gets confused about your organization membership.
Follow these steps in exact order to resolve this issue:
If you created an account on desktop but can’t log in on mobile (or vice versa), follow these steps:
Common causes:
Solution:
When signing in with Microsoft, you might see a “Need admin approval” message followed by “Tallyfy API - unverified”. This occurs when your organization’s Azure Active Directory settings require administrator consent before employees can use third-party applications.
What’s happening: Your company’s IT policies restrict which apps can access Microsoft accounts. Tallyfy needs explicit approval from an administrator before any user can sign in with their work Microsoft account.
Immediate workaround for users:
Permanent solution (requires IT administrator):
Your IT administrator needs to approve Tallyfy in Azure Active Directory:
Once approved, all employees can use Microsoft sign-in immediately. The consent only needs to happen once per organization. If you see error code AADSTS900144 after returning without consent, this confirms the admin approval requirement.
Additional resources:
When Tallyfy images load slowly or fail to appear, these targeted solutions can improve performance:
chrome://flags in the address bar, search for QUIC, set it to Disabled, and restart Chrome to resolve connection issues.The following section contains comprehensive guides for resolving issues in specific web browsers:
Troubleshooting > Clear cache in Chrome
Troubleshooting > Clear cache in Edge
Miscellaneous > Login and session errors
Troubleshooting > Clear cache in Firefox