Checkout behaviour when the DQE API is slow or unreachable

Support DQE
Support DQE
  • Updated

Symptom: the DQE API is slow, returns errors or is unreachable. You want to know whether checkout is blocked, whether a default value is applied, or whether validation is bypassed.

Affected versions: 1.0.0.

Short answer

  • Address: no blocking. Validation is skipped and checkout continues.
  • Address suggestions and complements: empty list, with no error message.
  • Phone: no blocking, no message.
  • Email (in the browser): no message and no blocking.
  • Email (server side, if DQE email validation is enabled): the email is considered invalid and may be refused. This behaviour differs from the other components.

There is no retry and no default value. There is no explicit bypass: the degraded behaviour is implicit.

Details per component

ComponentBehaviour on error
Address validation on submit (RNVP)The error is ignored and the form is not blocked.
Address suggestions (SINGLEV)No suggestion is displayed (empty list).
Address complement (COMPLV)No option is displayed.
Email, display in the browserNo message and no blocking.
Email, server sideThe cartridge treats the email as not valid. A customer who registers or updates an email during a DQE outage may see it refused.
PhoneNo server-side check. Nothing is displayed in the browser.

Timeouts, circuit breaker, rate limit

The service template delivered with the cartridge defines the following values:

ParameterTemplate value
Timeout5000 ms
Rate limit100 calls / 1000 ms
Circuit breaker10 calls, 500 ms

These values can be overridden in the site's Business Manager: check the values actually active on your instance. The credentials (user ID and password) are empty in the template and must be filled in for each instance.

Diagnosis

  1. In Business Manager, check the communication logs of the dqe-address, dqe-email and dqe-phone services.
  2. Search the logs for errors raised by the DQE cartridge.
  3. Check the service configuration (URL, credentials, licence) in Business Manager. The licence key is read from the site preference dqeLicenceCode: if it is missing, the service fails with the error dqe.service.no.licencecode.
  4. Reproduce the case on a test instance by cutting access to the API or forcing a timeout.

Related to

Was this article helpful?

0 out of 0 found this helpful