I’m writing this from a technical/user perspective — I work around software enough to recognize the difference between a device issue and a backend state problem.The app started off phenomenal. I uploaded multiple tracks, trained my preferences, and was able to generate genres and ideas almost instantly. For the first few days the responsiveness and output quality were honestly impressive.Then, after heavier usage, creation suddenly stopped working. No crashes, no clear error — generation simply never initializes. I tried the expected troubleshooting steps: reinstalling the app, clearing data, deleting local recordings, and starting fresh. Nothing changed. That strongly suggests the failure isn’t client-side but tied to the account or a server-side job queue.From a developer standpoint it feels like my account got stuck in a processing state, hit a silent rate limit, or was deprioritized after high usage. The UI still allows creation, but the backend never executes the request. Because of that mismatch, the app appears functional while being unusable.It went from an extremely engaging creative tool to something I currently cannot use at all. I’m hoping the team can reset the account state or improve error transparency — even a simple “queue / cooldown / processing” indicator would make a huge difference.Right now it feels less like a bug and more like the system quietly throttled heavy users without feedback.I contacted support via email a week ago and received no response.
Thank you for taking the time to provide such a detailed and technically thoughtful explanation. What you’re describing is not expected behavior. If generation is triggered in the UI but never executed server-side, this could indeed indicate an account-state or job queue related issue.We would like to manually review your account status and generation history. Please contact us again at beinthouch@oceanfloarmobile.com with the email linked to your account, your device model, and iOS version so we can investigate this with priority. We will also check why your previous support message did not receive a response.We appreciate your feedback regarding transparency around queue/cooldown states — improvements in this area are already being considered.