When something genuinely breaks, the fastest way to get it fixed is a clear, technical bug report sent directly to the official support address: support@coderevolution.ro. This channel goes straight to the people who build and maintain Aimogen, not to a generic help desk.
Bug reports are for reproducible problems, not usage questions or feature ideas. If something does not work as documented, behaves inconsistently, or fails under conditions where it should not, this is the correct place to report it.
A good bug report starts with context. State clearly that the message is about Aimogen, include the plugin version, your WordPress version, PHP version, and whether the issue happens in admin, frontend, automation, REST API usage, or chatbots. If the problem appeared after an update, mention that explicitly.
Describe what you were trying to do, what you expected to happen, and what actually happened instead. Avoid assumptions. Stick to observable behavior. “This should work” is less useful than “This feature stops execution after step X with no output.”
Execution Logs and Usage Logs are critical. If AI execution is involved in any way, logs should always be attached or pasted. Without logs, most AI-related bugs cannot be diagnosed reliably. Logs turn a report from guesswork into something actionable.
If the issue is visual, screenshots or short screen recordings help. If it is related to configuration, mention whether the setup was imported, migrated, or created manually. If automation or scheduled rules are involved, say so. These details matter.
Do not include API keys or sensitive credentials in bug reports. Logs do not expose keys, and keys should never be shared by email. If a provider connection is involved, simply state which provider and model were used.
Bug reports sent to support@coderevolution.ro are reviewed directly. If the issue is confirmed, it is either fixed or queued depending on severity. If more information is needed, you’ll be contacted. Clear reports are resolved faster because they reduce back-and-forth.
Bug reports should not be submitted through community channels or comments when they involve real malfunctions. Community spaces are great for discussion, but confirmed bugs belong in direct support.
In short, when something is broken, email support@coderevolution.ro, explain the problem precisely, attach logs, and avoid speculation. Aimogen is built to be debuggable, and good reports are the fastest path from “this is wrong” to a real fix.
