Troubleshooting and support

Start by identifying the request, expected result, and the point where work diverged. A useful support report distinguishes missing context, restricted access, a pending decision, and a system action with an uncertain result.

Identify where the work stopped#

Record what was requested, what completed, and what remains unresolved. Include the time and the relevant case or run reference if your deployment provides one. Avoid assuming the whole workflow failed when only one dependency is blocked.

For a content issue, identify the incorrect statement or missing section and the expected result. For an action issue, identify the affected system and whether a change may already have happened.

Check context and access#

Confirm that the relevant source exists, applies to the correct record, and is available under the approved access model. Ask the source owner to resolve conflicting information rather than substituting a guess.

If access has changed, involve the system owner. Do not work around a denied operation by copying restricted information into a request or broadening permissions without review.

Review pending or uncertain actions#

Check whether the workflow is waiting for clarification or approval through the configured channel. Contact the assigned owner when the next decision is unclear.

If a write or external action may have completed, verify its state before retrying. Include evidence of any partial completion in the handoff. Use the recovery process agreed for the deployment; do not assume repeating a request is harmless.

Prepare a support request#

Provide a concise report through your agreed support channel or Coryntas Console Support:

• The intended outcome and the relevant request reference.
• The expected behavior and what actually happened.
• The approximate time and affected system.
• Any pending approval or recent source or permission change.
• The steps already taken and whether an action may have completed.

Use approved references and share only what is needed to investigate. Never include passwords, API keys, or private tokens. The team can agree on a suitable process if additional evidence is necessary.