There are limits on the total number of products that can be requested from the RPG. For dedicated and supplemental connections, a maximum number of 300 products can be requested. Any requests above 300 products will be truncated at 300. Your local RPS list length is only limited by that total number of products. For WAN connections (backup or dedicated), a maximum of 65 products can be requested. As a result, the following are good practices:

• Include products that are most important at the top of your local RPS list.
• Most of the products on the national RPS List are distributed over the SBN and available to all offices. However, bandwidth limitations on the SBN usually result in offices receiving products from a subset of locations. You should create your WAN connection local RPS List to augment what you receive via the SBN. That will allow you to get the most products possible. Just make sure your office is requesting the national list of products over the SBN for the site(s) you are interested in!
• It’s possible, albeit rare, that you will experience either a significant latency or not receive products over the SBN. For these situations, you may want to have an alternate local RPS list for WAN connections. In this situation, include the lowest few elevation angles of your base products and any key derived products you need first to ensure you get what you need. NOTE: This issue should not be common.
• If you suspect that products are being truncated, you can review the log files for the RadarServer on your DX1/DX2 machine to investigate further. The command is:  more radarserver.log | grep -i truncated.
• For non-transmitting sites, you can mitigate load shedding when it occurs by removing any derived products that you receive over the SBN first. Since you should receive these products anyway, you may be better served to, at worst, get these products late than potentially not get other products at all.