Help

🔧 Troubleshooting Guide

Can't Connect to Org

Symptom: "Unauthorized" error or "Session expired" when trying to query data.

Quick Fixes

  1. Refresh the Salesforce page (F5 or Cmd+R). TrackForcePro re-fetches your session token.
  2. Log out and log back in to your Salesforce org to refresh your session.
  3. Uninstall and reinstall the extension if the issue persists.

Why It Happens

  • Your Salesforce session token expires after 30 minutes of inactivity
  • You logged out of Salesforce but TrackForcePro still has an old token
  • Browser cookies were cleared (TrackForcePro relies on them to fetch your session)

SOQL Queries Are Slow

Symptom: SOQL query results take 10+ seconds to display.

Diagnosis & Solutions

  1. Check your query complexity — Large JOINs, subqueries, and LIKE patterns are slow. Simplify if possible.
  2. Check your record volume — If you're querying 100k+ records, Salesforce naturally slows down. Add more filters to reduce results.
  3. Check your network — Open browser DevTools (F12) → Network tab. Is the request taking long to complete, or is it rendering the results that's slow? If rendering, try switching to "Raw" view instead of the virtualized table.
  4. Check API limits — If you're approaching your org's daily API limit (checked in Org Tools), Salesforce throttles requests. Run fewer queries and wait for the daily limit to reset at midnight.
Pro Tip: Use the SOQL Builder's pagination to limit results per query (add "LIMIT 1000" to your query). This is much faster than loading all 50k results.

Missing Data in Queries

Symptom: Query results show fewer records than expected, or a field is blank.

Likely Causes

  • Field-level security (FLS) — You don't have READ access to the field. Check your user profile in Salesforce Setup.
  • Sharing rules — You don't have read access to those records. Check object sharing rules and field sharing.
  • Deleted records — Records you queried might have been deleted by another user since your last query. Re-run the query.
  • Org-specific custom fields — If you query a custom field that doesn't exist in another org, the query fails silently.

How to Verify

  1. Open the SOQL Builder and check your WHERE clause
  2. Open Salesforce directly and verify the records/fields exist
  3. Check your Field-Level Security: Setup → Users → Your Profile → Field Permissions

Can't Inline Edit Fields

Symptom: "Inline edit disabled for this org" message when trying to edit a field.

Solutions

  1. Check Settings — Go to Settings → Inline Edit Permissions and enable editing for your org
  2. Check field permissions — Make sure your profile allows UPDATE on that field (Setup → Profiles → Field Permissions)
  3. Check object permissions — Make sure your profile allows UPDATE on the object itself
Security Note: Inline edit is disabled by default for production orgs. This is intentional to prevent accidental changes. Enable it only if you're comfortable with quick edits.

Extension Crashes / Service Worker Error

Symptom: "Service worker crashed" notification or extension stops responding.

Recovery Steps

  1. Refresh the Salesforce page (F5). This restarts the content script.
  2. Close and reopen the extension popup to restart the service worker.
  3. Clear browser cache — Browser DevTools → Application → Storage → Clear All.
  4. Uninstall and reinstall the extension if steps 1-3 don't work.

Why It Happens

  • Service workers are subject to Manifest V3 memory limits. Large queries or many simultaneous requests can cause crashes.
  • Browser memory is low or the OS is under heavy load
  • Extension got into a bad state (rare, but recovery is simple)

Cross-Browser Issues

Chrome / Edge

Most stable. If issues occur, follow the standard troubleshooting above.

Firefox

  • Issue: Some API calls fail or return 403 errors
  • Cause: Firefox MV3 implementation is different from Chrome/Edge
  • Fix: Disable any Firefox add-ons that intercept API calls (proxy tools, adblockers with aggressive filtering)

Opera

  • Issue: Opera uses Chromium but has a smaller user base, so edge cases may appear
  • Fix: Same as Chrome/Edge. If persistent, try Chrome instead.

Performance Tips

  • Minimize open tabs — Each open tab uses memory. Close unused Salesforce tabs to free resources.
  • Limit simultaneous queries — Don't run 10 SOQL queries at once. Run them in batches of 2-3.
  • Use pagination — Add LIMIT clauses to your SOQL queries (e.g., "LIMIT 1000") instead of fetching all 50k records.
  • Disable unused shortcuts — Go to Settings → Sidebar Settings and toggle off shortcuts you don't use. Reduces sidebar render time.
  • Monitor org limits — Check Org Tools → Org Limits regularly. If you're near your API limit, slow down queries.

Frequently Asked Questions

Does TrackForcePro store my data?

No. All data stays in your browser and on Salesforce's servers. TrackForcePro doesn't upload anything to external servers (except when you explicitly export).

Is inline edit safe to use on production orgs?

Proceed with caution. Inline edit is powerful but risky on production. We recommend disabling it for production orgs in Settings, and only enabling it for sandboxes where changes don't impact live users.

Can I use TrackForcePro in a sandbox org?

Yes! TrackForcePro works in any Salesforce org (production, sandbox, scratch org). All features work the same.

What if I have more than one org open?

TrackForcePro tracks each org separately. Settings, saved collections, and org-specific toggles are per-org. You can have TrackForcePro open on Account records in Org A and Contact records in Org B simultaneously, and they won't interfere.

Does TrackForcePro work on mobile?

Partially. The extension works on mobile if your browser supports it (Chrome Mobile, Firefox Mobile), but the UI isn't optimized for small screens. Desktop is recommended.

Can I export data from TrackForcePro?

Yes. Most tabs support exporting query results as CSV or JSON. Look for an "Export" button in the results area.