None of that helps obtain the information this request is asking for. It’s better to not go off topic from the original thread to tell someone information they may already know, since this isn’t development support.
On topic, it would be really helpful if the warnings gave this information.
Haha, what? I’m explaining why this happens, how to avoid it, and how to debug it properly which OP is having trouble with. It already tells you the key that was throttled, script is irrelevant.
Edit: If the key isn’t being displayed, you should report that as a bug. Requesting a feature that is literally just a work-around for the bug makes no sense.
Would be great if this also applied for WaitForChild and object parenting without yields warnings.
@BuildIntoGames that has nothing to do with the original post; he may be writing to this DataStore from different scripts and the conditions under which each happens may be different, so it’d be much easier to identify where the problem is if the script and line were provided.
Full support. Been having a lot of datastore throttling issues recently even though I’m nowhere near the API limit so I’d really like to know the trace of where the issue is being caused by.
@BuildIntoGames I only access datastores 5 times per minute, when a player joins, when they leave, and when the game closes. I am using pcalls and not making repeated calls. Do explain how not including a trace with warnings will help me solve this.