Issue
Players report lost progress, but server output does not identify the affected store or operation.
Cause
Errors are swallowed by broad pcall blocks and the project has no per-operation telemetry.
Fix
Record the operation type, store, sanitized key category, retry count, server job ID, and result. Use Roblox DataStore observability dashboards to compare error and throttle changes over time. Never log secret or sensitive player content.
Verify
Force a controlled failure in a test universe and confirm the dashboard and server log identify the same operation.
Official Roblox DataStore observability update
#1
Original Heliotrope guidance with authoritative Roblox sources.