> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/use/existing-dialogue-cloud-neo-connect-apps/wallboard/troubleshooting.md).

# Troubleshoot Wallboard

Basic checks for Wallboard startup, connection, display, and log issues.

Use these basic checks when Wallboard does not work as expected. The checks are intended for supervisors or end users. They do not replace setup or configuration work by an administrator.

## Restart Wallboard

Restart Wallboard first. Wallboard uses external components and tries to restore itself, but restarting closes the application and starts new connections.

Expected outcome: Wallboard reconnects and starts showing the expected view again.

## Check that Wallboard shows the expected setup

Check whether Wallboard is showing the expected UCC, view, and skill.

If Wallboard cannot connect, check whether the configured URL is reachable in your environment. If you do not manage the Wallboard setup yourself, ask your administrator or support team to verify the configuration.

Expected outcome: Wallboard connects to the intended UCC and shows the intended view.

## Check the UCC, skill, and signed-in agents

If Wallboard connects but does not show the expected data, check whether:

* The UCC is running. If you have access to operational status information, see [Service health](/operate/monitor-and-troubleshoot/service-health.md).
* The UCC has a skill with `ShowOnWallboard` enabled. Administrators can verify skill configuration in [Skills and Routing Criteria](/contact-center-configuration/queues/skills-and-routing-criteria.md).
* Formal agents have signed in. Agents can use [Sign in and manage your profile](/use/handle-conversations/webagent/sign-in-and-profile.md) for WebAgent sign-in guidance.

Expected outcome: Wallboard can receive information for the active UCC, visible skills, and signed-in agents.

## Check the log file

Wallboard creates a log file in the local user profile:

```
%Appdata%\Local\WORKSTREAMPEOPLE\Wallboard\Application.log
```

The log file records events from Wallboard. For example, it can include connection events.

To inspect the log:

1. Copy the log to another location so Wallboard can keep writing to the active file.
2. Open the copy in a text editor.
3. Go to the date and time of the issue.
4. Read the event description.

Expected outcome: You find log entries that help support or your administrator understand what happened at the time of the issue.

## Contact support

If the basic checks do not resolve the issue, contact support.

Include:

* Wallboard version.
* Log files.
* Date and time of the issue.
* Scenario description.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/use/existing-dialogue-cloud-neo-connect-apps/wallboard/troubleshooting.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.