Report a problem with useful evidence
Clear evidence helps support reproduce and resolve an issue without repeatedly asking for basic details.
Overview
Clear evidence helps support reproduce and resolve an issue without repeatedly asking for basic details.
Check the cause before repeating an action
Begin with the exact reference and the current page. A wrong status view, old search term, date filter or organization assignment can hide an existing record. Clear irrelevant filters and confirm the account before assuming that data has been lost. An application link remains private even when it was supplied through a public guide.
A missing button or rejected request can reflect permissions, record status, location, assignment or required form fields. Read the full validation message and inspect the latest details. Do not change unrelated record data or create another account simply to bypass a restriction. The responsible company administrator can check organizational access.
If the issue persists, preserve the page URL, time, record references, visible message, attempted steps and expected result. After a connection interruption, verify whether the operation already succeeded before repeating it. Send one support ticket and follow replies in that conversation. This is especially important for order creation, payment recording and logistics transitions.
Steps
- Record the page URL, approximate time and affected record references.
- Describe the steps you took and the expected result.
- Copy the visible error message and attach a screenshot that shows the relevant controls.
- Remove private information that support does not need, then open one ticket and follow replies there.
Good to know
After a network interruption during a save, check whether the record or action already succeeded before submitting again. This helps avoid duplicate records or financial entries.
Application links
Application links require the appropriate account access. The destination is selected for your signed-in role.