Start in your own words. The diagnosis asks only questions that can change the solution and, when the answer is not certain enough, prepares a structured support request without making you start over.
Loading guided troubleshooting…
Reproduce the behavior in the simplest possible context and change only one variable at a time.
Record the page or module, approximate time, what you expected and what you observed.
Reproduce the case simply and change only one variable at a time.
Keep the exact message, a non-sensitive reference and a cleaned screenshot if useful.
Open the specialized article that matches the observed symptom before changing several settings.
Review the causes that may limit the display of proposed periods.
Read the article → TerritoriesUnderstand why an address may be rejected by the configured service areas.
Read the article → PriceCompare the options, additions, and discounts that make up the summary.
Read the article → PromotionDiagnose the entry, status, and eligibility conditions of a benefit.
Read the article → SurveysCheck the trigger conditions and customer contact details available.
Read the article → ValidationWhen an operation is rechecked, the server may reject it or recalculate its result under the applicable rules. This behaviour may be normal and, by itself, is not enough to conclude that there is a system error.
Read the article →Use the diagnostic checklist to record the facts, then the support-request guide if the issue remains.
Learn how to compare expected and observed results, verify source data, and test a comparable case.
View the diagnostic checklist →Structure the steps, impact, evidence, and checks already performed.
Prepare the request →Keep useful evidence before trying again, without sending passwords, secrets, sensitive payment information or unnecessary personal data.
