ES 
EN 
DE 
ZH cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
A failed power module is expensive enough without a dispute over who pays. Learn which warranty clauses, RMA steps, and root-cause rules to clarify with your IGBT or SiC module supplier before you place the order.
A power module can pass incoming inspection, survive validation, and still become a costly dispute eighteen months later, when a returned unit lands on a failure-analysis bench. Who pays for the replacement? Who decides the root cause? How long will the investigation take? Buyers who ask these questions after a failure often discover the answers were never written down. This guide lists the warranty and RMA (Return Material Authorization) terms that procurement and design teams should clarify with any IGBT or SiC module supplier before the purchase order is signed.
Why Warranty and RMA Terms Deserve Attention Before the PO
Power modules sit at the heart of inverters, chargers, drives, and UPS systems, so the commercial stakes of a single failure are high. Four factors make clear terms essential:
- High unit value and downtime cost. One failed module can idle an entire converter or production line.
- Ambiguous failure signatures. Stress from the application and defects from manufacturing can look almost identical on the bench.
- Long time lags. Wear-out and latent defects may surface years after the date code.
- Layered supply chains. Buying through a distributor or an OEM can change who actually owns the warranty claim.
Warranty Terms to Clarify Before You Order
Vague wording such as “standard warranty applies” is a common source of disputes. Ask for definitions, not adjectives. The table below summarizes the clauses most worth confirming in writing.
| Término | What to Clarify | Por qué importa |
|---|---|---|
| Warranty period and start date | Duration, and whether it runs from shipment, invoice, date code, or commissioning | A start date tied to date code can quietly shorten your coverage |
| Remedy | Replacement, repair, credit, or refund, and who chooses | Determines your real recovery after a confirmed claim |
| Covered failure modes | Which defects and wear-out conditions are included | Prevents arguments over what counts as a “manufacturing defect” |
| Exclusions | Overvoltage, improper mounting, gate-drive faults, ESD, unauthorized disassembly | Defines the boundary between supplier and buyer responsibility |
| Storage and handling limits | Allowed storage time, temperature, humidity, and packaging | Long inventory holding can affect eligibility |
| Trazabilidad | Serial or lot coding, and records retained for a claim | Allows a failure to be tied to a production batch |
| Liability cap | Whether consequential or line-down costs are covered | Often the largest gap between expectation and reality |
| Change notification | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits. cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits. cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits. cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits. cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits. cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
- cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits. cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
|---|---|---|
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
| cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits | cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits |
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits Coffin-Manson lifetime prediction for power modules. Insulation-related returns often trace back to design rules covered in our article on creepage and clearance for high-voltage modules.
How to Reduce RMA Risk Before It Happens
The strongest warranty position is a failure that never occurs. These habits lower both the odds of a return and the odds of a dispute:
- Capture waveforms early. Record turn-off overshoot, gate voltage, and short-circuit response during validation, and keep them on file.
- Log by date code. Record which lots went into which production batches so any problem can be traced quickly.
- Verify thermal assumptions. Measure junction and case temperature rather than relying on simulation alone; our overview of junction temperature in power modules covers the main methods.
- Match the driver to the device. Gate drive and protection settings should follow the module’s requirements, which is where an IGBT and SiC gate driver selected with the supplier helps.
- Track device-specific reliability topics. For SiC, read about body diode degradation and forward voltage drift and add post-stress checks to your plan.
- Inspect incoming stock. Verify packaging, labeling, and basic electrical parameters before modules enter long-term storage.
Ask About the Quality System Behind the Warranty
A warranty is only as dependable as the process that supports it. Three questions help separate a documented system from a promise:
- Which quality certifications does the supplier hold, and can you see the certificate? For automotive-related programs, IATF 16949 is the automotive quality management system standard and is a common reference point.
- How are changes communicated? JEDEC publishes a standard for notifying customers of semiconductor product and process changes (JESD46, since superseded by J-STD-046). Ask whether the supplier follows a formal change-notification process.
- What is checked before shipment? Look for specific controls such as void inspection and electrical testing, not general statements about quality.
HIITIO’s Sobre Nosotros page describes a quality system with 23 quality control checkpoints, 100% X-ray void inspection, dynamic and static electrical testing, and HTRB testing. It also cites certifications such as IATF 16949 and compliance with IEC 60747, 60749, and 60068 standards, with production in a 10,000-class cleanroom environment. Use this kind of published detail as a starting point, then ask any supplier, including us, to confirm the scope in writing.
Get Clear Warranty and RMA Terms Before You Commit
Reliable modules and clear paperwork go hand in hand. HIITIO Semiconductor offers IGBT such as the HCG200FH120A2D (1200 V, 200 A, 62 mm half-bridge), as well as módulos SiC such as the HCS200FH120A2C1 (1200 V, 200 A, 62 mm half-bridge, 175 °C maximum junction temperature). Share your application, voltage class, cooling method, and expected volume with our engineers, and we will recommend a suitable module along with the datasheets and documentation you need for your qualification file. Ask our team to provide warranty and RMA terms in writing together with your quotation, so every clause, from start date to failure-analysis reporting, is agreed before the first shipment. Our technical and customer support is available around the clock, and custom solution requests receive a tailored recommendation within 24 hours. cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits
cURL Too many subrequests by single Worker invocation. To configure this limit, refer to https://developers.cloudflare.com/workers/wrangler/configuration/#limits.
