You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description: It has been observed that inactive symbols (trading pairs that have been removed from the platform) no longer display any historical data in the Bitfinex Reports app. While I understand that the pair is no longer supported for trading, it is important for a reports app to still provide access to all the data and transactions that were performed while the pair was active.
Could you please look into ensuring that historical data for inactive symbols is still accessible and displayed in the reports, as it is critical for users to analyze past transactions even after the trading pair is no longer available?
Expected Behavior:
Historical data (including trades and other relevant information) should remain accessible for inactive symbols in the Bitfinex Reports app.
The app should display the available data, even if the pair is no longer actively traded on the platform.
Actual Behavior:
No historical data is displayed for inactive symbols that have been removed from the platform.
I appreciate your attention to this matter!
The text was updated successfully, but these errors were encountered:
Description: It has been observed that inactive symbols (trading pairs that have been removed from the platform) no longer display any historical data in the Bitfinex Reports app. While I understand that the pair is no longer supported for trading, it is important for a reports app to still provide access to all the data and transactions that were performed while the pair was active.
Could you please look into ensuring that historical data for inactive symbols is still accessible and displayed in the reports, as it is critical for users to analyze past transactions even after the trading pair is no longer available?
Expected Behavior:
Actual Behavior:
I appreciate your attention to this matter!
The text was updated successfully, but these errors were encountered: