Fixed intermittent collection error (500)
An intermittent "Server responded with 500" collection error affecting some users has been fixed. The issue began on April 16 at 2:25 AM KST and was resolved on April 23 at 10:30 PM KST.
Scope of impact
- This did not affect all users — it only occurred intermittently for those who changed plans or had gaps in collection during the period
- Snapshots during the error were not saved, but data recovers automatically on the next successful collection
We apologize for the inconvenience. Everything is working normally now.