FrontierzDocs

Troubleshooting

A short list of issues you might hit and what to do about them. If something is not on this page, ask whoever manages Frontierz at your organization.

My microphone is not working

The AI Fellow needs microphone access to hear you. If the call opens but no one hears you speak, it is almost always a microphone permission issue.

Check the microphone icon in your browser's address bar. If it shows a blocked or muted state, click it.
Allow microphone access for the Frontierz site.
Reload the page and start the call again.

If your computer has more than one microphone (a built-in one and a headset, for example), check the operating system's audio settings to make sure the right one is selected as the default input device.

Screen sharing does not work

Screen sharing relies on your browser's native sharing dialog. Some browsers and some operating systems require an additional permission the first time:

  • macOS: open System Settings, then Privacy & Security, then Screen Recording. Allow your browser. You may need to quit and reopen the browser after granting permission.
  • Windows: screen sharing usually works without extra setup. If it does not, check that the browser is up to date.
  • Linux: behavior depends on the desktop environment.

If your browser does not support screen sharing at all, switch to a recent version of Chrome, Edge, Firefox, or Safari.

I cannot send a file

You can only send a file after the session has started. If Frontierz says to start a session first, begin the conversation and try again.

If the session is already active, check the file itself:

  • Send one file at a time.
  • Use a supported format, such as PDF, Word, PowerPoint, text, or image.
  • Try a smaller file if the upload is rejected.

If a document keeps failing, convert it to PDF or ask your administrator to add it to the AI Fellow's reference material.

Sign-in links are time-limited and single-use. If the link no longer signs you in, request a new one:

Open the Frontierz URL given to you by your organization.
Enter your email address.
Open the new email and click the new link.

If the email is not arriving:

  • Check your spam folder.
  • Confirm with your administrator that the email address Frontierz has on file is the one you are entering.
  • Ask whether your organization's email gateway might be blocking Frontierz emails.

I see "Access denied" on an AI Fellow

Private AI Fellows require access from an administrator. If you see the access-denied page, you have not been added to that AI Fellow's access list. Ask the person who shared the link, or your organization's administrator. See When access is required.

I cannot see my Learning Path

Either you are not enrolled in it, or you are enrolled in more than one and a different one is set as active.

  • Open Profile and check the active Learning Path selector. If the selector lists the path you expected, switch to it. See Switching between Learning Paths.
  • If the path you expected is not in the list, you are not enrolled. Ask your administrator to enroll you.

The AI Fellow misunderstood me

Restate the point and continue the conversation. The AI Fellow re-evaluates as you speak and can correct an objective that was marked complete too early. If a specific objective keeps tripping the AI Fellow up, name the objective directly and explain how you are demonstrating it. The AI Fellow can usually catch up.

If a response is wrong in a way that matters (a factual error, an inappropriate comment, or a security concern), end the call and tell your administrator. Administrators can review the transcript and follow up.

The page froze or reloaded mid-session

Open the same session again from Your Journey. If the conversation interrupted before any objectives were completed, the session is still your current one. If the AI Fellow had started checking off objectives, those remain checked, and you can resume the conversation from where it left off.

If the issue is repeatable, switch to a different browser or restart the browser entirely. A persistent issue is worth flagging to your administrator with the time it happened, so the platform team can investigate.

On this page