Forums
(@mr1ime)
3 days, 13 hours ago
Found the cause — it’s caching. With LiteSpeed Cache’s “Cache REST API” option enabled, the bug reliably reproduces. Disabling it and purging cache fixes it immediately