Report a bug or technical issue
If something is broken in the Flinque influencer marketing platform, we want to know about it. This page explains how to report bugs effectively, what happens after you submit, and how to track resolution.
Just need to report something?
Skip the guidance and go straight to the form. We will follow up with questions if needed.
- All severities accepted
- Workspace details auto-attached
- Reply received within SLA window
- Status updates as we investigate
When to report a bug vs ask for help
Use this page for reproducible defects, not general support questions.
✓ Report a bug if
- A feature does not work as documented
- You see error messages or crashes
- Data appears incorrectly or is missing
- Buttons or links do not function
- Layout is visibly broken
- Integrations fail or sync incorrectly
- You can describe steps to reproduce
→ Use other channels for
- How-to questions → Help Centre
- Feature requests → Improvement Feedback
- Account access issues → Technical Support
- Service outages → System Status
- Billing issues → Contact
- Data privacy requests → Data Removal Policy
Bug severity guidelines
When reporting, indicate severity to help us prioritize. We may adjust the level after triage based on technical impact.
What to include in a great bug report
A complete bug report saves rounds of follow-up questions and gets fixes faster. The form prompts for these fields, but here is what each one means.
Summary
One sentence describing the issue. Example: “Campaign export to CSV produces empty file when more than 50 creators are selected.”
Steps to reproduce
Numbered list of every action needed to see the bug. Be specific. Even small details (which menu, which click order) matter.
Expected behaviour
What should happen if the feature worked correctly. Reference docs or prior behaviour if relevant.
Actual behaviour
What actually happens. Include exact error messages, error codes, and any unexpected output.
Browser and device
Browser name and version, operating system, screen size if relevant. Helps us reproduce in the same environment.
Frequency
Always, intermittent, or one-time. If intermittent, note any pattern (time of day, specific data, after certain actions).
Screenshots and recordings
Visuals make debugging dramatically faster. Screen recordings showing the steps in action are even better than screenshots.
Workspace details
Auto-attached when you submit through the in-app widget. Manual reports can include your workspace URL or ID.
What happens after you report
Every reported bug goes through a structured triage and resolution process.
Acknowledged
You receive a confirmation email with a tracking ID, typically within minutes.
Triaged
Within SLA window, our team reviews, reproduces, and confirms severity.
Investigated
Engineering investigates root cause and scopes a fix. You may receive follow-up questions.
Resolved
Fix is deployed. You receive notification with details, and the bug appears in release notes.
Resolution timelines
Bug fix timelines depend on severity and complexity. These are typical targets, not guarantees.
Tracking your reported bugs
Every bug report has a unique tracking ID. You can:
- Reply to your acknowledgment email to add new info
- Reference the tracking ID when contacting support about the same issue
- Receive automatic updates when status changes (triaged, in progress, resolved)
- Find related fixes in our release notes
Frequently asked questions
What if my bug report is closed without a fix?
Sometimes reported behaviour turns out to be intended (we will explain), or we cannot reproduce it. If you disagree with the resolution, reply to the closure email with additional context. We will reopen if warranted.
Can I report security vulnerabilities through this form?
Please use our dedicated security disclosure process instead. See our Security Policy for vulnerability reporting details and our responsible disclosure commitments.
Can I report bugs anonymously?
No. We need to be able to follow up with questions and notify you when fixes ship. Your contact details are kept private and used only for the bug investigation.
What if I report something that is actually a feature request?
Our triage team will reroute it to the Improvement Feedback queue and let you know. Your input still gets considered, just through the right channel.
Will I get credit for finding bugs?
For meaningful bug reports that lead to user-impacting fixes, we sometimes credit reporters in our release notes (with permission). For security disclosures, see our security disclosure recognition program.
Report it now and help us improve Flinque
The faster we know, the faster we can fix it for you and every other Flinque customer.