Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more

If a cloud GPU request fails, first determine whether you hit a quota limit or the provider lacks capacity for that GPU in that location. A quota increase can resolve the former, but it cannot create physical capacity. Then check compatible regions and GPU types, consider a reservation or queued provisioning for planned work, use Spot only if your workload can recover from interruption, and improve scheduling or utilization if your platform can share existing hardware.

Diagnose why the GPU instance is unavailable

The message “GPU unavailable” does not identify one universal problem. Check the exact error and distinguish a project or account quota ceiling from a shortage of physical GPUs. These constraints call for different responses: request a quota change only when the rejection is quota-related; if the requested hardware is not available, try a compatible location or provisioning path instead.

Google Cloud describes quota as a project-level limit and says on-demand accelerator requests are subject to availability rather than guaranteed fulfillment. In practice, check three things: whether your project can request the accelerator, whether the GPU model is listed for the intended region or zone, and whether capacity is available when you submit the request. A quota approval addresses the limit, not the supply of hardware. Google Cloud’s GPU quota documentation and GPU documentation explain the relevant constraints.

Free tools Windows power users keep installed

One-click scans. No signup required.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Keep the error message and request details while troubleshooting. Record the project or account, requested accelerator, region or zone, and whether the failure explicitly names quota. That information helps separate a limit you may be able to change from a capacity issue that requires a different location, timing, or provisioning option. Do not infer that a retry, quota request, or location listing has resolved the problem until the instance is actually provisioned.

#1 Best Overall
Sale
Compressed Air Duster,130000RPM Super Power Cordless Air Duster,Rechargeable Brushless Blower,3 Gear Adjustable Blower with LED Light,Dust Remover for Computer/House/Outdoor/Car
  • Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
  • With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
  • Wide Application:Upgraded attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
  • Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
  • Warranty & Support: Our Electric air duster comes with 5 years warranty and 24/7 customer service. During this period, if you have any questions,pls kindly feel free to contact us.

Use this fallback ladder

  1. Read the exact failure and check quota. Determine whether the provider rejected the request for quota or whether the requested capacity could not be provisioned. Avoid treating a quota request as a fix for a capacity shortage.
  2. Check locations and compatible hardware. Look up the requested GPU model by region and zone, then test another compatible location or accelerator if your workload permits. A location listing narrows the search; it does not guarantee that a GPU can be provisioned immediately.
  3. Plan around reservations or queued provisioning. For work that can wait, investigate reservation choices or a queued option such as Google Cloud Flex-start. Verify the selected option’s timing, quota prerequisites, billing, and cancellation terms before committing.
  4. Use Spot only if interruption is acceptable. Confirm that the job can save progress, resume or restart safely, and tolerate time lost during recovery. Spot capacity is reclaimable, not a dependable substitute for uninterrupted compute.
  5. Improve allocation when hardware exists to share. For supported Kubernetes or managed GPU environments, make sure workloads request GPU resources correctly and are scheduled on eligible nodes. Consider supported sharing features where the workload and hardware allow them.

This is a decision sequence, not a promise that one rung will always work. If the workload has a hard deadline, weigh the time needed to test an alternate location or accelerator against the time available. If it can wait, queued provisioning or a planned reservation may be reasonable to investigate. If it cannot tolerate interruption, do not choose Spot simply because it appears to be an available option. If there is no eligible hardware in the platform, scheduling changes cannot produce it.

Check another region, zone, or GPU type

Use the provider’s GPU location documentation to see where the requested model is listed. Google Cloud publishes GPU availability by region and zone; check its GPU locations page for the specific accelerator you need. A listed location is not a real-time capacity signal, so still test provisioning in the console or through your normal request process.

If you broaden the search, do not assume that a different GPU is interchangeable. Before switching, validate GPU memory, software and driver/runtime support, interconnect requirements, and the workload’s scaling behavior. A region change can also affect data residency, network transfer costs, and latency to users or dependent systems. The right alternative depends on the actual model and workload; the cited documentation does not identify a universally suitable replacement accelerator.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Make the alternate-location decision explicit rather than treating “another region” as a free substitution. Ask whether the data is permitted to reside there, whether moving input and output data changes transfer costs, and whether the application can tolerate the resulting latency to users or connected systems. Likewise, a different GPU type must fit the workload’s memory and software requirements and its interconnect needs. If any of those are unknown, test the changed configuration before moving a time-sensitive or production workload.

Location documentation is useful for narrowing the search, not for predicting the result of an individual request. Availability is account-, region-, zone-, GPU-, and time-dependent. A model shown as available in a location does not mean capacity is available at the moment you request it. Check current account-specific availability through the provider’s normal request process.

Reserve capacity or queue planned work

Reservations and queued provisioning are planning tools, not promises of immediate recovery. Google Cloud documents reservation options and Flex-start provisioning. Flex-start resources are provisioned when capacity becomes available, and Google Cloud documents GPU and TPU Flex-start resources as running uninterrupted for up to seven days. That is a product-specific documented limit, not a general cloud guarantee or an estimate of how long a request will wait. See Google Cloud’s reservation overview and Flex-start VM documentation for the current options.

Rank #2
EVEO® Screen Cleaner Spray Kit (Streak-Free) TV Screen Cleaner for Smart TV, Lcd, LEd, Oled | Computer Screen Cleaner Spray and Wipe Microfiber Cloth - TV, Monitor, Laptop, iPad, Car - 6.7oz 1 Pack
  • Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
  • Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
  • Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
  • Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
  • Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth

Before relying on a reservation or queued request, confirm the precise reservation window, required quota, billing treatment, and cancellation rules for your account and selected option. An idle reservation can have cost implications; compare that exposure with the cost of waiting or adapting the job. Do not plan around an assumed lead time unless the provider confirms it for your requested capacity.

What’s actually slowing this PC down?

Pick the symptom - the matching free tool is one click away.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

These options solve different planning problems. A reservation is something to evaluate against its particular terms and window; a queued option such as Flex-start means waiting for capacity to become available. Neither should be described as an immediate fallback without checking what the provider commits to for the selected option and account. For queued provisioning, build the wait into the schedule rather than assuming a particular start time. For a reservation, understand whether you are paying for time when the GPU is idle and what happens if the work no longer needs that capacity.

Before committing, verify the prerequisites and costs using current documentation. In particular, check quota requirements, reservation dates or window, billing, and cancellation terms. No universal lead time, price, or service guarantee for these choices is established in the cited documentation, so avoid planning around an unconfirmed estimate.

Decide whether Spot GPUs fit the workload

Spot can be useful when lower-priority, interruptible capacity is acceptable, but its defining trade-off is that the provider can reclaim it. Google Cloud documents that Spot VMs may be preempted at any time with a 30-second warning. DigitalOcean describes Spot GPU Droplets as suitable for fault-tolerant work that can save progress, restart, and move to another instance; it also says it may reclaim Spot GPU node pools when it needs the capacity. These terms establish interruption risk, not a particular frequency of interruption. See Google Cloud’s Spot VM documentation, DigitalOcean’s Spot GPU Droplets documentation, and DigitalOcean’s Spot Kubernetes documentation.

Good candidates

  • Batch training or other jobs that checkpoint often and can resume correctly.
  • Workloads that can retry, migrate, or run on another available instance without corrupting results.
  • Tasks where the team can absorb interruption and recovery time.

Poor candidates

  • Latency-sensitive production endpoints that must remain continuously available.
  • Long-running work without reliable checkpoints or a tested restart procedure.
  • Workloads whose recovery process takes so long that interruption erases the practical benefit of using Spot.

Before moving a job to Spot, test checkpoint creation and restore, confirm that outputs remain consistent after a restart, and decide where checkpoint data will live. Include recovery time and any storage or data-transfer costs in the decision; compute price alone does not represent the total cost of an interrupted run.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The right question is not simply whether training can be run on Spot, but whether this particular training job can resume safely. Checkpoint frequency determines how much work may be lost between saves; recovery procedures determine how long it takes to continue after an interruption. Test a restore, check that results remain consistent, and make sure the job can restart or move without corrupting outputs. A job that can technically restart but takes a long time to recover may still be a poor fit if interruptions erase the practical benefit.

Rank #3
BladeHawks RGB Gaming Mouse Pad Extra Large Extended 31.5x12 Inch-Black
  • 【Large size】:Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
  • 【LED backlight mouse pad】:Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
  • 【Anti-slip rubber base】:Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
  • 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
  • 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.

Google Cloud’s documented 30-second warning is a product-specific fact, not a guarantee that every interruption will be predictable or that another provider gives the same notice. DigitalOcean’s documentation says Spot GPU node pools may be reclaimed when capacity is needed. Neither source establishes how often a particular user should expect reclamation. Plan around the possibility of an interruption rather than inventing a frequency or assuming a warning window common to all Spot services.

Improve GPU scheduling and utilization

If the obstacle is allocation across a platform rather than a complete lack of hardware, correct scheduling and supported sharing features may help use available GPUs more effectively. Kubernetes supports custom GPU resource requests for containers. Its documentation also describes Node Feature Discovery for discovering and labeling GPU-enabled nodes. Check that the workload requests the appropriate GPU resource and that its pod can be scheduled onto a node that exposes the required accelerator. See Kubernetes GPU scheduling documentation and Node Feature Discovery documentation.

Google Cloud documents GKE GPU time-sharing and Multi-Instance GPU as ways to allocate existing GPU capacity. Sharing can improve utilization when workloads are compatible, but it does not add physical GPUs or remove every isolation and performance trade-off. Check hardware support and test the workload before adopting either feature. See GKE GPU sharing documentation.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

For Kubernetes, verify the whole scheduling path: the container’s resource request must specify the GPU resource it needs, and the scheduler must have an eligible node that exposes that accelerator. Node Feature Discovery can discover and label GPU-enabled nodes; labeling helps identify nodes, but is not the same thing as creating capacity. A workload that cannot be placed because its request or node eligibility is wrong may need a scheduling correction. A workload that has no suitable GPU nodes still needs a capacity solution.

Time-sharing and Multi-Instance GPU are utilization tools to evaluate when there is hardware to allocate. They may allow existing capacity to serve compatible workloads more effectively, but sharing is not equivalent to receiving an additional physical GPU. Confirm that the hardware supports the chosen feature and test workload compatibility, performance, and isolation expectations. Do not enable sharing as a blanket workaround for every job, especially when the workload’s requirements are not known.

Compare the remaining options against your constraints

Option Time to access Capacity certainty Interruption tolerance What to verify
Retry on-demand in the same location Immediate attempt Subject to availability; a request is not guaranteed Usually suited to work that expects ordinary instance continuity, but capacity is not assured at request time Quota, current capacity, and whether retrying changes the request conditions
Try another compatible location or GPU Potentially faster access if capacity is available there Not guaranteed by a location listing Depends on the workload and how it handles a changed location or accelerator GPU memory, runtime compatibility, interconnect, latency, data residency, and transfer costs
Reservation Planned access; terms depend on the selected option Depends on provider and reservation terms Depends on the reservation and workload arrangement Window, quota prerequisite, billing, and cancellation rules
Queued provisioning such as Flex-start Wait for capacity to become available Provisioning is capacity-dependent, not immediate Google Cloud documents Flex-start GPU/TPU resources as uninterrupted for up to seven days Current product terms, account eligibility, quota, and workload duration
Spot Depends on available reclaimable capacity Interruptible; provider may reclaim capacity Requires reliable checkpointing, restart, retry, or migration Interruption handling, recovery time, checkpoint storage, and output integrity
Improve scheduling or share existing GPUs Depends on eligible hardware already available Does not create physical capacity Sharing can involve performance or isolation trade-offs Resource requests, eligible GPU nodes, hardware support, and workload compatibility

Compare total cost rather than just the hourly compute rate: include reservation idle time, storage, network or data movement, and engineering work to change scheduling, checkpointing, or fallback automation. No comparable current provider prices or universal price ranking are established here, so check live terms for the exact configuration you would use.

Rank #4
Sale
Vaydeer Wrist Rest for Keyboard and Mouse, Computer Ergonomic Wrist Support Pad, Soft Memory Foam Arm Cushion for Desk, Palm Hand Office Laptop Typing
  • 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
  • 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
  • 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
  • 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
  • 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.

The choice is a trade-off across more than speed. A same-location retry is an immediate attempt, but on-demand fulfillment remains subject to availability. A different location or GPU type may offer another path, but it adds hardware-fit and data/latency checks. A reservation or queued option is more appropriate to planned work than an urgent assumption of immediate capacity. Spot is an option only when interruption and recovery are tolerable. Scheduling changes matter only if eligible hardware is already available.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Include operational burden in the comparison. A GPU change can require testing runtime and memory fit; Spot requires checkpoint and restart work; a location change may involve data movement and residency checks; Kubernetes scheduling and sharing require configuration and compatibility checks. A fallback that saves time at provisioning but takes substantial engineering effort or has high recovery cost may not be the best alternative for the current job.

There is no supported universal price ranking among these options in the provider documentation. Compare the current terms for the exact configuration, and count more than running compute: idle reservation time, storage for checkpoints, network or data movement, and engineering effort all affect total cost. If the workload is deadline-bound, include waiting and recovery time in the comparison as well as the stated compute charges.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Make the fallback operational before the next shortage

A fallback works only if the workload can actually run there. For a job that may move across locations or GPU types, record its hardware requirements and test the driver, runtime, and memory fit on the alternative. For Spot or queued execution, make checkpoint and restart behavior part of the job design rather than relying on manual recovery after an interruption.

  • Record the requested GPU model, region or zone, quota, and the exact provisioning error.
  • Define acceptable alternate regions and GPU types, including data and latency constraints.
  • For interruptible work, choose a checkpoint interval that limits tolerable lost work and test a restore.
  • For Kubernetes, verify GPU resource requests and node labels before scheduling a production job.
  • Set a decision point for when to wait, switch, or defer, based on the work’s deadline and recovery cost.

A useful fallback policy can state what to do for each failure mode. If the error is quota-related, review the relevant quota path. If the requested GPU is not available in the selected location, consult the location information and test only those alternate regions or GPU types that meet the workload’s requirements. If planned work can wait, evaluate reservations or a queued option under its current terms. If Spot is considered, require a tested checkpoint and restart path. If the workload is on Kubernetes, verify resource requests and eligible nodes before changing the infrastructure plan.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

That policy should also say when not to switch. Do not move data to another region until residency, latency, and transfer implications are understood. Do not change accelerator types without checking memory, software, driver/runtime, and interconnect fit. Do not rely on Spot for a workload that cannot tolerate interruption. Do not expect GPU sharing or better scheduling to solve a shortage when no eligible hardware is available.

Best Value
Sale
Under Desk Cable Management Tray No Drill, Metal Mesh Cable Management Under Desk with Clamp Mount, 2 Hole Cable Tray with Wire Management and Cord Organizer for Home Office Standing Desk
  • 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
  • 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
  • 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
  • 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
  • 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.

Availability changes by account, region, zone, GPU, and time. Provider documentation describes the available mechanisms, but cannot establish that a particular reader can provision a specific accelerator now. Confirm current console availability and account-specific terms before making a time-sensitive commitment.

Frequently Asked Questions

What is the difference between GPU quota and GPU capacity?

Quota is a project-level or account limit on what you may request; capacity is whether the provider can supply the physical accelerator in the requested location at that time. A quota increase can address a quota rejection, but it does not create physical capacity. Check the exact error and then verify the GPU model and location.

Does a GPU listed for a region mean I can provision it now?

No. A provider’s GPU location page helps identify regions or zones where a model is offered, but it is not a real-time capacity signal or guarantee of immediate provisioning. Check account-specific availability through the normal request process.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Can I use Spot GPUs for training?

Possibly, if the training job can checkpoint, resume or restart correctly, and tolerate recovery time. Google Cloud says Spot VMs may be preempted at any time with a 30-second warning; DigitalOcean says it may reclaim Spot GPU node pools when capacity is needed. Test checkpoint restore and output integrity first. A long job without reliable checkpoints is a poor fit.

Will a reservation or queued provisioning get me a GPU immediately?

Not necessarily. Reservation terms depend on the selected option, while Google Cloud Flex-start resources are provisioned when capacity becomes available. Check the current reservation window, quota prerequisites, billing, and cancellation rules. Do not assume a lead time unless the provider confirms it for your account and requested capacity.

Can Kubernetes scheduling or GPU sharing fix an unavailable GPU?

It can help when eligible GPU hardware already exists but workloads are not being allocated correctly or existing capacity can be shared. Kubernetes supports GPU resource requests, and Node Feature Discovery can discover and label GPU-enabled nodes. GKE GPU time-sharing and Multi-Instance GPU can improve use of existing capacity when supported and compatible, but they do not add physical GPUs.

How should I compare the cost of alternatives?

Compare the full cost for the exact configuration, not just compute while running. Include reservation idle time, checkpoint storage, network or data movement, and engineering effort to change scheduling or build fallback automation. The cited documentation does not establish comparable current prices or a universal provider price ranking, so verify live terms.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The Bottom Line

Start with the failure itself: quota and physical capacity are different problems. Then check the requested GPU and location, and choose a fallback that fits the workload’s hardware, data, deadline, and interruption constraints. Reservations and queued provisioning need planning; Spot needs tested recovery; scheduling and sharing only help when suitable hardware exists. Verify current account-specific availability and terms rather than assuming a listed GPU or alternative guarantees access.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.