@tradingTech

In general, there is no limit on RFA side, the limit you are talking should be the limit on TREP side or Provider server you are connecting to.

Each time you send a streaming request (InitialImage | InterestAfterRefresh) for a new item, it will increase a total number of item limit for your user on infra side.

There are cases such as aggregate item limit exceed, when a total number of opening items has exceeded a limit per user. But it seems not to be this case because you should receive the status message instead of the Refresh.

We still need RSSL tracing log to confirm issue you are experiencing and if possible you may test the RICs with our example such as StarterConsumer so it can generate application log(StarterConsumer_<pid>.log) which contains all messages it receives from infra. Then you can review the logs and compare with RSSL tracing to see if it has an error.

Note that you can open a new API support case to investigate the issue further.

@tradingTech

What version of RFA.NET you currently use?

As far as I understand if the new subscription reaches the maximum limit on TREP, you should get response status message instead of receiving Refresh message. But in this case, you already get the new Refresh message but no update.

Maybe the RIC does not have an update at the time you request. Or it could be an issue on TREP side. Can you please turn on RSSL tracing log when testing the application?

You can find a configuration for turn on RSSL tracing log from the following post . We can see what are incoming and outgoing messages from the RSSL tracing log.

The dll I'm using is called RFA8_NET140_x64. I will turn on logging again and see what I get.

Just confirming, does the amount of instruments I request an initial image for impact how many subscriptions I'm allowed? I'm only attempting to subscribe to ~25 bonds.