Reference

Start troubleshooting

Choose a safe guide for a sign in, access, work, service, storage, log, or backup problem.

Choose the problem

Keep the first evidence

Write down what the person tried to do, the tenant, the time, the exact message, and any request, run, job, case, or item ID.

Do not collect passwords, sign in codes, tokens, private keys, Connection secrets, or copies of customer information that are not needed.

Change one thing at a time

  1. Read the visible message.
  2. Check the item in the product.
  3. Use the matching guide.
  4. Change only the most likely cause.
  5. Check the result before making another change.

Start with access when an area is missing

A missing area can be a correct restricted state. Do not treat it as a broken page until Check access shows that the exact action should be allowed.

Only registration is available

Read Fix registration and renewal problems when normal Product areas and exports are blocked.

Keep the diagnostic reference

If the browser shows a client incident reference, keep it alongside the request, operation and run IDs. A client reference helps correlate a failure; it does not prove the server received or completed the action. Read current work state before retrying. Follow Prepare diagnostic information for Support when a reviewed bundle is needed.

Pūnaha Docs

Search the guides

Enter at least two characters.

    Product screen

    View the full screenshot