Thank you @rahul . As you may know, there are normal lags in our indexing processes. When we are free of bugs in our system/processes, our own internal indexing process can take 24 hours to run. That is, it can take our system 24 hours to index new registrations from the time of submission processing completion (where we verify and register the input XML) to where we completely index that DOI and record (convert the input XML to JSON). From there, third-parties, like Semantic Scholar / ResearchGate, can retrieve the metadata in our APIs, but they may have lags in their systems and processes as well.
What I can tell you is that DOI 10.38124/ijisrt/25aug323 was successfully registered with us on 2025-August-08 at 12:18:59 UTC. But, when our system went to index that work in our REST API (convert it from XML to JSON), the process failed. That process has been failing for a fraction of records registered with us since 8 July when we migrated our data center to the cloud. And, it is continuing to fail for a small percentage of registrations each day. We’re working on fixing that and will be manually re-pushing records to our API a couple of times per week until we fix the bug.
Our technical team manually re-pushed DOI 10.38124/ijisrt/25aug323 and nearly 1.4 million other records registered between 3 and 14 August on 14 and 15 August. DOI 10.38124/ijisrt/25aug323 is now present in all of our APIs. Here it is in our REST API: https://api.crossref.org/works/10.38124/ijisrt/25aug323
You can see it was indexed on 15 August. You can also confirm that DOIs and their full records are in our system by using our search interface at search.crossref.org, like this: Crossref Metadata Search
At this stage, all third-party systems should be able to retrieve and use the metadata associated with DOI 10.38124/ijisrt/25aug323.
Apologies for the delay,
Isaac