Wrong Current Era in Metadata response - Githubissues

subscan-explorer / subscan-issue-tracker

The issue tracker for Subscan.io.

3 stars 5 forks source link

Wrong Current Era in Metadata response #80

Closed CerratoA closed 6 months ago

CerratoA commented 7 months ago

Confirmation

[X] My issue isn't already found on the issue tracker.
[X] I have read the Subscan API documentation (if it seemed to be an API bug).

Affected Network(s)

Polkadot

Steps to reproduce

Make a call to the metadata endpoint: /api/scan/metadata
Wait for the response.
Check the response data.current_era.

Expected output

The response data.current_era as of today December 7, 2023 should return 1284.

Actual output

The response data.current_era as of today December 7, 2023 it's returning 1282 which is December 5 Era.

Additional factoids or references

Is there a way to know the sync status of the source data used by Subscan to provide the response?

freehere107 commented 6 months ago

@CerratoA Thanks for your feedback. This issue has been fixed.