Report a bug
Tell us what went wrong
Every report is stored the moment you send it and read by a person, not an auto-responder. If you have a screenshot or a short screen recording, attach it: it usually removes an entire round trip of questions.
If live orders are affected right now, email instead
This form is read within a working day. Anything that is costing you money as you read this goes to support@quantgrid.in with URGENT in the subject. The platform runs 8:00 AM to 5:00 PM IST; outside those hours it is offline by design, which is worth ruling out first on the status page.
What helps
Three things that make a report actionable
None of these are required. Each one measurably shortens the time between you sending this and us knowing what happened.
What you did, in order
The steps that led to it, not just the end state. “Switched copying on at 13:50, then placed a NIFTY order on the master” tells us where to look; “the copy did not work” does not.
When it happened, with the clock
A time to the minute, in IST, and the broker account it concerns. Our logs are timestamped, so a time turns a report into a search rather than a hunt.
What you expected instead
Half of all reports turn out to be behaviour working as designed. Saying what you expected is what separates a defect from a surprise, and both are worth telling us about.
The report
Send it
Have an idea rather than a defect? The feature request form is the right place, and it goes to the same queue.
Found a security issue?
Do not use this form. Security reports have their own route, their own disclosure terms and a commitment not to pursue anyone who reports in good faith.