A Candela GentleMax Pro can stop delivering output for reasons that fall into several evidence groups, including user-error conditions, manufacturer-defined interlock events, consumable and optics records, and connection or cooling conditions, and the cause cannot be assigned from the symptom alone. The clinic’s task is to record the symptom, error message and operating context safely, then escalate with preserved evidence to a qualified party for diagnosis.

This guide owns safe symptom evidence and escalation for the GentleMax Pro. It is written for clinic owners, biomedical engineers and service leads who need to document an output failure without performing repair work. It does not provide disassembly, electrical testing, calibration, bypass or repair instructions, and it does not answer the inspection or service-cost decisions, which belong to their own guides.

The most common mistake in an output-failure event is converting a symptom into a cause too quickly. A system that stops during a firing sequence can look identical from the operator side across very different underlying conditions, so the only safe response is to document the observable facts completely and let the qualified diagnostic process assign the cause.

Set the response rule before an event occurs: stop use, record, preserve, escalate. The rule applies to every output failure, regardless of whether it repeats, and it keeps the clinic inside the safety boundary that protects both the staff and the system.

Record the reported symptom, error message and operating context

Record the symptom in the operator’s own words and the exact error message or code as displayed, with the time and date. Do not translate the message into a diagnosis; quote it. The record should also state when the failure appeared: at power-on, during standby, at the start of a firing sequence or during a treatment sequence.

Record the operating context: which handpiece or delivery device was in use, what the system was doing, how long it had been operating and whether the failure repeated when the sequence was attempted again. Context is evidence, because the same message at different moments supports different diagnostic paths.

Photograph the message and the control state where possible, and note the system and software state if it is visible in the operator interface. The photographs anchor the event to a point in time and preserve the display state that later records will be compared against.

Also check:  How Much Does a Hydrafacial Machine Cost in 2026?

Do not clear the error and continue to test. A reset that makes the message disappear does not resolve the underlying condition, and repeated operation after an output failure can turn a documentation event into a safety or warranty event.

Note laser-head, optics-cooling and connection state without disassembly

At the visible level, record the state of the laser head or handpiece, the optics-related surfaces, the cooling openings and the connections, without opening the system. Visible findings include damage, dust, debris, obstruction, moisture, loose connections and signs of prior repair; each is recorded as an observation, not as a cause.

Check the cooling openings for visible obstruction and note whether fans operate during a documented demonstration, without removing covers. Visible cooling condition is a finding; cooling performance under load is a qualified test question.

Record the connection state of the handpiece, delivery arm and cables at the visible level: secure, loose, worn or damaged. A loose connection is an observable fact that belongs in the record; whether it explains the failure is a diagnostic question.

Do not open panels, remove covers, measure electrically, adjust optics or operate the system beyond the documented demonstration. Every one of those steps is qualified service work, and performing it without authorisation changes the meaning of all later evidence.

Separate user-error evidence from manufacturer-defined interlock and flashlamp records

Separate the evidence into three groups: user-error evidence, manufacturer-defined interlock evidence and consumable records such as flashlamp history. User-error evidence covers operating steps that fall outside the documented use; interlock evidence covers system-defined conditions that stop operation by design; flashlamp records cover the consumable state the system may rely on. The three groups have different records and different resolutions.

For user-error evidence, record what was done before the failure: the operator steps, the configuration used and any deviation from the documented procedure. A deviation is a finding, not an accusation, and it belongs in the record for the qualified review.

For interlock evidence, record the message, the moment it appeared and the system state. Interlock events are designed stops; whether the stop was correct requires the qualified party to review the event against the manufacturer-defined conditions.

For flashlamp and consumable records, request the dated installation, usage and service history for the components involved. Flashlamp status is a documented consumable fact; without the record it is unverified, and an unverified consumable state cannot be used to explain the failure.

Also check:  Why Is Regenerative Aesthetics Outsmarting Volume Fillers in 2026?

Set safe shutdown and qualified-escalation conditions

Shut down the system safely following the documented procedure when output stops or when an error appears, and do not restart it to test whether the problem has passed. Safe shutdown is the operator’s final permitted action in the event; everything after it is evidence preservation and escalation.

Define the escalation conditions in the clinic’s procedure: any repeated output failure, any message the staff do not understand, any visible damage, moisture or unusual behaviour, and any event involving an interlock or safety condition. The conditions are written before the event so escalation does not depend on judgement under pressure.

Escalate to a qualified party with the preserved evidence: the symptom record, the error message, the context, the visible findings and the consumable records. The escalation file should state what was observed and what remains unknown, so the service provider can plan the diagnostic work without repeating the operator’s steps.

Quarantine the system or its components if the event involved visible damage, moisture, unusual odour or any condition that could affect safety. Quarantine means the system is not used and is identified as unavailable until the qualified review is complete.

Define what a qualified diagnostic record must contain

A qualified diagnostic record must name the system and software state, the components tested, the method, the instruments, the date, the person or organisation performing the diagnosis and the findings. A record without these fields is an opinion, not a diagnosis, and it cannot be applied to the unit.

The record should answer the questions the clinic asked: which evidence group the failure belongs to, what was tested, what was found and what was corrected. It should also state what was not tested, because the limits of the diagnosis are part of the diagnosis.

Keep the diagnostic record with the clinic’s own event file so the two can be compared. The comparison shows whether the qualified finding matches the documented symptom, which is the basis for accepting the work and for any warranty or service claim that follows.

Do not accept a diagnostic summary that names no unit, no method and no date. The clinic’s role is to request the attributable record, not to interpret it, and the request should be made in writing so the service file is complete.

Also check:  What Are the Technical Requirements for Shipping Sensitive Optical Equipment Like Aesthetic Lasers?

Define evidence required before the system returns to service

Evidence group What it can show What it cannot show Record required
Symptom record What the operator saw, when and in what context The cause of the failure Dated message, context and photos
Visible findings Observed damage, moisture, obstruction or connection state Internal or output condition Dated observations without disassembly
User-error evidence Operating steps before the event Whether the steps caused the failure Written operator steps and deviations
Interlock evidence A system-defined stop occurred Whether the stop was correct Message, moment and system state
Flashlamp and consumable records Dated installation, usage and service history Output performance Attributable records matched to serial
Qualified diagnostic record What was tested, by whom, with what result Future reliability Attributable, dated report

Before the system returns to service, require the qualified diagnostic record, a documented corrective action that names the unit and the finding it addresses, and a successful follow-up verification performed under the documented method. The system returns to service on the record, not on the fact that the message disappeared.

Keep the full event-to-return file with the unit record. If the failure recurs, the new event is compared against this file, which is how the clinic distinguishes a resolved issue from a repeating one and how the service provider inherits the complete history.

When the output-failure event is handled, review Candela laser systems and request current condition, compatibility, remaining-use, inspection, shipping and warranty evidence in writing. The symptom-evidence register becomes the first document in the service file, and every later service event is compared against it.

Frequently Asked Questions

Can a clinic restart a GentleMax Pro after an output failure to see if it works?

No. Repeated operation after an output failure can turn a documentation event into a safety or warranty event. Shut down safely, record the symptom and escalate with the preserved evidence.

Does a visible pass mean the system is safe to use again?

No. Visible condition is separate from internal and output state. Return to service requires a qualified diagnostic record, a documented corrective action and a successful follow-up verification.

References