> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rivi.software/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Recover from failed loads, unsaved changes, conflicts, and access problems.

Preserve unsaved work before reloading an editor. Read the message on screen, then use the matching recovery action.

## Saving and connection states

| State | What to do |
| - | - |
| Unsaved | Keep the editor open and save or wait for autosave |
| Saving | Wait for confirmation before leaving or publishing |
| Saved | The server acknowledged the change |
| Disconnected | Check your connection and preserve text before reloading |
| Conflict | Compare with the latest saved revision before discarding or reapplying edits |

**Load latest revision** or **Reload and discard edits** replaces local changes. Copy important text first if you need to preserve it. A failed save should not be treated as a successful one just because the editor still displays your text.

## A list looks empty

Confirm the active station and selected date range. Clear search and status filters. In Today, check broadcast assignments; in Planning, inspect the full calendar. Ask an administrator about access if the module or record is unavailable.

## Loading failed

Use the screen's retry action. If the message says the session expired, sign in again. If your station access changed, ask an owner to review membership and permissions. Repeatedly refreshing cannot restore a removed permission.

A refresh warning may leave the last loaded data visible. Check its timestamp and warning before relying on it. Switching stations loads the new station's data separately.

## Live controls stopped responding

Check connection status and who holds presenter control. After reconnecting, confirm the active item before retrying an action. A takeover requires confirmation, and live control commands do not replay automatically.

## Publication failed

Open the record and review required fields, approval, embargo, media references, and any job error. Save the corrected revision, obtain review again if required, and reschedule. **Approved** alone does not mean **Published**.

## Report a persistent problem

Give your station administrator or support contact the station name, screen, action, approximate time and timezone, and any request or reference ID shown. Describe whether the work was saved and which recovery action you tried.

Do not include passwords, API tokens, backup codes, or confidential preview links in the report. See [API errors](/radiotools/api-reference/errors-and-versioning) for integration troubleshooting.


## Related topics

- [Daily work](/radiotools/daily-work/index.md)
- [Today](/radiotools/daily-work/today.md)
- [RadioTools help](/radiotools/index.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.