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

# When something is missing, loading or not working

> Check the right things and collect useful details without needing server access.

<Note>
  This guide includes features awaiting release. If an option is not available in your workspace, contact StackShift Support.
</Note>

## What you can do

Check the right things and collect useful details without needing server access. Where to find it: The affected Support screen.

## Before you start

* The name of your workspace and the time the problem occurred.

## Steps

<Steps>
  <Step>
    Check the selected workspace and live or test environment. A new environment may correctly have no channels, articles or community yet.
  </Step>

  <Step>
    For an empty feature, follow its setup guide. For an access message, ask your owner to check your role and inbox access. For no available billing plans or a service reported unavailable, contact StackShift rather than trying to configure its servers.
  </Step>

  <Step>
    If a read stays on loading or Try again, retry it once and check your connection. Sign in again if the session expired; save any unsent text first where possible.
  </Step>

  <Step>
    If a send, payment or action timed out, inspect the original operation’s status before repeating it. Use the existing retry or verification action.
  </Step>

  <Step>
    If the issue continues, send Support the screen name, workspace, environment, approximate time, error/request identifier and a redacted screenshot. Do not send passwords, keys, tokens or card details.
  </Step>
</Steps>

## Example

Channels is empty in test but populated in live: switching environments explains the difference without reconnecting the account.

## Things to know

* A blank page and an empty list are different. An endless spinner or repeated error after valid setup should be reported.
* A refresh may discard unsent drafts. Check uncertain sends before creating a replacement.

## What happens next

<Check>
  You either resolve a setup/access problem or provide enough context for Support to investigate the real failure.
</Check>

## If something goes wrong

<Warning>
  * No request identifier visible: include the exact error text and time instead.
  * Another teammate can perform the action: compare roles and inbox access, not their passwords.
</Warning>

## Related guides

<CardGroup cols={2}>
  <Card title="Get started with StackShift Support" href="/stackshift-support/frontend-integrations-and-request-states">
    Create your workspace, connect an inbox, answer customers and recover interrupted actions.
  </Card>

  <Card title="Support channels and message recovery" href="/stackshift-support/channel-reliability">
    Connect supported inboxes, preserve message history, and recover interrupted delivery safely.
  </Card>

  <Card title="Choose a plan and understand your usage" href="/stackshift-support/billing-and-plans">
    Review prices, staff allowances, conversation usage, storage and AI credits before paying.
  </Card>
</CardGroup>


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