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

# Troubleshoot access and model runs

> Learn how to use the Dunsky Cloud Platform: troubleshoot access and model runs. Guidance based on the core-app repository.

Use the message shown by the Dunsky platform to distinguish access problems, input problems, and failed model runs. Record the model and run identifier before requesting help.

| Symptom | What to check |
| - | - |
| Application unreachable | Correct environment address and VPN where required |
| Runner unavailable | Client accounts use guided scenarios |
| No study available yet | Ask the Dunsky study team to make the study available |
| Study could not load | Use Retry and retain the displayed error if it persists |
| Invalid input | Review the selected model and its expected input structure |
| Job failed | Read the returned job message and inspect available logs |
| Job aborted | Rerun when appropriate or contact the modelling team |
| Prepared download expired | Request preparation again |

## Progress display

The runner displays a fixed intermediate progress value while a job is running. It is a status indicator, not a measured estimate of work completed or time remaining. Use **Completed**, **Failed**, and **Aborted** to identify terminal outcomes.

## Ask for help

Share the environment, model, tag or run identifier, exact error, and steps that produced it with your Dunsky team. Avoid sending credentials or unrelated client data.


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