Reporting an Issue

When to report an issue

Use the issue reporter to tell the FloopFloop team about a bug or problem with the platform itself— for example a page that crashes, a button that does nothing, a layout that breaks on your device, or an action that returns an unexpected error.

For questions about how to use a feature, or for help with content your AI project generated, the support page and FAQs are usually a better fit.

How to open the report dialog

You can open the issue reporter from two places:

• The site footer— Look for the "Report an issue" link in the Support column. This works from any page on the platform.
• The support page— A dedicated card lets you open the same dialog without scrolling to the footer.

You must be signed in to submit a report. If you are not signed in, the dialog shows a sign-in link instead of the form.

What the form captures

You only need to fill in two fields:

• Title(required) — A short summary of the issue. The clearer the better — for example "Save button on project settings does nothing in Safari".
• Severity(optional) — Pick how blocking the issue is: low, medium, high, or critical. Use critical only when the platform is unusable.

You do notneed to write a long description — the report automatically captures the technical context that engineers need to investigate:

• The exact URL where the issue happened
• Your browser and operating system (user agent)
• Your interface language
• The project ID, if you opened the dialog from a project page

What happens after you submit

Reports go straight into the FloopFloop support queue, where the team can review them, change their status, and turn them into actionable tickets for engineering. You will not get an automated reply, but if the team needs more information they may contact you on the email address attached to your account.

Rate limit

To prevent spam, you can submit up to 5 issue reports per hour. If you have a long list of bugs, group similar ones into a single report when you can.