Reference

Troubleshooting

Symptom-keyed fixes for common problems in ScreenerHub — empty results, missing fields, login failures, and notification issues.

6 min read

Troubleshooting in ScreenerHub starts with the symptom, not the feature. Find the description below that matches what you are seeing, follow the steps, and use the linked guides if the issue continues.

My screener returns no results

An empty result set almost always means the active criteria are collectively too narrow — not that there is a data problem.

What to check:

  1. Remove one filter at a time and rerun after each removal. This isolates which rule eliminates all candidates.
  2. Look for conflicting logic. Requiring a P/E below 10 and revenue growth above 50 % in the same screen is rare by definition, not a bug.
  3. Review your universe constraints. A combination of exchange, country, sector, and market cap can leave an empty eligible set before any metric filter runs.
  4. Check units. Market cap fields may be expressed in millions or billions depending on the column — the field tooltip confirms the unit. A threshold set in the wrong unit silently excludes everything.

When stuck, open a template that approximates your strategy and compare its criteria against yours. Templates are calibrated to return non-empty results across major markets.

A field I expect is missing

Not every field is available for every market. Coverage depends on vendor sourcing, the exchange, and your plan tier.

What to check:

  1. Use the Studio field search to confirm the exact name. Some metrics have multiple formulations — "EV/EBITDA" and "Enterprise Value to EBITDA" are the same field.
  2. Check your plan. Certain advanced metrics are restricted to paid tiers. A lock icon in the field panel signals that an upgrade is required.
  3. If the field appears in the column list but returns blanks for specific stocks, that is a vendor coverage gap rather than a missing field. See the data sources guide for per-field refresh cadence and coverage notes.

The result count changed since yesterday

Screener results reflect the current state of market data. Count changes between sessions are normal and expected.

Common causes:

  • Scheduled data refresh. Fundamentals update on a regular cadence. A company that reported earnings overnight may now pass or fail a valuation rule.
  • Price movement. Any filter that includes the current share price — P/E, P/B, EV/EBITDA — shifts whenever the price moves.
  • Corporate events. Stock splits, delistings, mergers, and exchange reclassifications alter the eligible universe without warning.
  • New listings. IPOs entering the database expand the universe.

If the count changed dramatically and none of the above apply, check the data sources guide to see whether a refresh was in progress at the time you ran the screen.

Numbers look wrong for a small or micro-cap stock

Data quality for small and micro-cap stocks is lower than for large caps. This reflects the coverage policies of financial data vendors and is not specific to ScreenerHub.

What to check:

  1. Open the company page and compare the value against the company's own investor relations disclosures.
  2. Check the freshness indicator on the data point. Small caps update less frequently than large caps for many fields.
  3. Treat extreme outlier readings — a P/E of 800, a debt-to-equity above 200, a negative book value — as signals to inspect the underlying financials directly rather than as confirmed facts to filter on.

For a full list of known limitations by data type, see the data sources guide.

I cannot save a screener

What to check:

  1. Confirm you are signed in. Saving a screener requires an account.
  2. Check whether your plan allows additional saved screeners. Free accounts have a limit on the number of saves. See plans and quotas for current limits per tier.
  3. If the save button is active but the operation fails with an error message, refresh the page and try again. If the error persists, contact support with the screener name and the exact error text — this helps diagnose server-side failures faster.

A monitoring run did not fire

Monitoring runs are scheduled events and depend on the data pipeline completing before they trigger.

What to check:

  1. Verify the monitoring set is active. A paused or disabled set does not generate runs.
  2. Open the run history inside Monitoring Lab. If a run entry exists but the result looks unexpected, the underlying data may have been unavailable or incomplete at trigger time.
  3. Runs fire after the nightly data pipeline completes — typically in the early morning hours. If you check before that window closes, no run entry will appear yet.
  4. On market holidays, some data vendors do not publish updates. A run on those days may produce no changes rather than a full result set.

For a deeper explanation of run timing and the history view, see the Monitoring Lab guide.

Email notifications are not arriving

What to check:

  1. Check your spam or junk folder. Transactional email lands there on first send more often than expected.
  2. Open account settings and confirm the email address is correct and verified.
  3. Confirm notification preferences are enabled. Monitoring alerts can be toggled independently from other email types.
  4. If you use a corporate email address with strict filtering rules, ask your IT team to whitelist the ScreenerHub sending domain.

Allow up to 15 minutes after a monitoring run completes before expecting the notification to arrive in your inbox.

OAuth login fails or loops

What to check:

  1. Clear browser cookies and try again. An expired session cookie is the most common cause of a redirect loop.
  2. Open a private or incognito window to rule out browser extensions interfering with the OAuth redirect.
  3. If you originally signed up with an email and password, attempting to sign in with Google or Apple using the same email address creates an account conflict. Use the original sign-in method or contact support to merge the accounts.
  4. Check that third-party cookies are not fully blocked in your browser settings. The OAuth handshake requires cookies to survive the redirect cycle.

Currency or locale display looks wrong

What to check:

  1. Open account settings and confirm your preferred currency and locale are saved correctly.
  2. After changing locale settings, a hard reload — Cmd+Shift+R on macOS, Ctrl+Shift+R on Windows — clears the cached layout.
  3. Stock prices always display in the trading currency of the exchange where the stock is listed. A converted value in your preferred currency appears in parentheses where the field supports conversion. If no converted value appears, that specific field does not support currency conversion.

What if none of these match

If your problem does not fit any symptom above, check the FAQ for broader product questions. When writing to support, include your browser name and version, the URL you were on, and a step-by-step description of what you did before the problem appeared. That information resolves most tickets in a single exchange.