HomeHelpTroubleshootingBrowser Requirements

Browser Requirements

Browser settings TravelFlow needs, how ad blockers break MFA sign-in, and why there is no offline mode or browser push.

All UsersLast reviewed 03 Aug 2026

Was this article helpful?

Related Articles

Common Errors

What the most common TravelFlow messages mean: Access Denied, session expiry, account lockout, rate limits, and "Failed to generate PDF".

Permission Issues

Check your role, understand the real role boundaries, and tell permission errors apart from lockouts and deactivated organizations.

Payment Failures

Diagnose declined cards, card tokenization errors, 3D Secure redirects, and duplicate card payments through PayU.

Previous

GDS Search Problems

Next

Mobile Usage

TravelFlow runs entirely in your browser. Nothing in the platform detects or blocks a particular browser, so an old one will not warn you — it will simply misbehave. Use a current version of Chrome, Edge, Firefox or Safari and keep it updated.

Cookies and Local Storage

JavaScript must be enabled, and the site must be allowed to use cookies and local storage. TravelFlow keeps your session identifier and your last-activity timestamp in local storage so that idle timeout and sign-out work consistently across tabs. If storage is blocked — for example in a hardened private window — the app still loads, but activity in one tab may not keep another tab signed in, and you can be logged out sooner than expected.

Ad Blockers and Privacy Extensions

Content blockers can break sign-in when multi-factor authentication is enabled, because the security check MFA relies on is loaded from Google. The symptom is the explicit message “Security verification is blocked. Please disable ad blockers or try a different browser.” Related messages are “Security verification timed out. Please refresh the page and try again” and “Security verification not ready. Please wait a moment and try again.” Disable the blocker for this site, or sign in from a different browser.

Safari's tracking prevention causes the same class of failure. If MFA verification will not complete in Safari, try Chrome or Edge before assuming your phone number or authenticator is at fault.

Offline Use and Browser Push

TravelFlow has no offline mode. There is no background worker installed in your browser, so every page needs a live connection, and browser push notifications are not delivered even though a Push notifications toggle exists under the Preferences tab of your profile. Rely on the in-app notification bell in the top navigation bar instead, and keep a tab open if you are waiting on something.

Recommended Screen Resolution

For desktop use, 1280 x 720 pixels or larger is comfortable. The layout is responsive and works on smaller screens, but wide accounting tables and multi-chart dashboards benefit from more width. See the Mobile Usage article for what to expect on a phone.

Clearing Cache to Fix Display Issues

If the interface looks broken, buttons stop responding, or styles are wrong after a platform update, clear your browser cache: press Ctrl+Shift+Delete (or Cmd+Shift+Delete on macOS), select cached images and files, clear, then reload the page.

Tip: Before reporting a display problem, retry in a private or incognito window with extensions disabled. If the problem disappears there, an extension or a stale cache is the cause.