# Troubleshooting and support

Sydekyks user and operator guide. Check feature availability and release-specific installation requirements.

Start with the failed run or the screen where the problem occurred. A specific error and the expected result help your administrator identify the cause.

## ​Check these first

- Confirm the selected Command Center and mission.

- Confirm whether you are looking at a draft or a published version.

- Open the most recent run and find the first failed step.

- Check the selected connection and target resource.

- Read the error from the connected app and compare the actual input with the expected value.

## ​Common problems

 | Problem | Next check

 | No run appears | Trigger configuration, published/enabled state, schedule time or incoming webhook delivery

 | Connection rejected | Expired credential, revoked access or missing provider permissions

 | Required field missing | Trigger sample, data-selector mapping and branch/loop context

 | Provider rate limit | Request volume, retry timing and provider quota

 | Run times out | Step duration, external service response and deployment timeout

 | Result appears twice | Duplicate events, retries and missing idempotency checks

 | A log does not show the whole input | Truncation and retention limits (https://docs.sydekyks.com/install/troubleshooting/truncated-logs)

## ​Report the problem

Contact the support route supplied for your deployment. Include the mission name, run time with timezone, failing step, error text, expected result and a redacted sample that reproduces it.

Do not include passwords, provider keys, raw customer documents or access tokens. Keep the run link inside the support channel authorized for your deployment. Your operator may also need the platform version and recent infrastructure changes.

For server problems, use the operator troubleshooting section (https://docs.sydekyks.com/install/overview).