@gowrisankar.dasarathan

Thank you for reaching out to us.

API uses CLOSED and CLOSED_RECOVER stream states.

Both states indidcate that the stream is closed but, for CLOSED_RECOVER, data can be recovered on this service and connection at a later time.

The followings are descriptions in the ETA developer guide.

I assume that Recoverable Close and Non-recoverable Close are used by RTDS or TREP. Please contact the RTDS support team directly via MyRefinitiv to answer this question.

@Jirapongse

we are aware of this one, and base on this document we are returning closed_recovered if we don't currently have a given symbol because our list of symbol is dynamic and they can be created and destroyed during the lifetime of the application,

we started questioning this approach as some of the Java clients appear to respond to that by trying to re-subscribe every few milliseconds, which made us questioned if that's a valid approach

@gowrisankar.dasarathan

I think the CLOSED_RECOVER is suitable for the items that can be recovered within few minutes because when the RTDS gets this CLOSED_RECOVER stream state, it will keep re-subscribe to that item until the stream is opened or closed.

I understand your use case but the application will not know when those items are created or destroyed.

In your case, you may need to publish a symbol list RIC that contains a list of active tiems. You can add and remove items in a symbol list RIC.

Then, a client application can subscribe to this symbol list RIC to check for active and inactive items.