Troubleshooting: Fix Every Common Issue Yourself in Under a Minute
Almost every issue on GigTry resolves itself with one of five moves: retry after 30 seconds, add one specific correction and regenerate, check the live status endpoint, verify your credit balance, or reconnect a platform in the automation area. This guide maps every common symptom to the exact fix — no support ticket required.
| Symptom | What it means | Fix it yourself |
|---|---|---|
| "Generate" did nothing / shows busy | Free AI capacity is momentarily saturated — the system queues honestly instead of faking success | Wait ~30 seconds, click Generate again. Check gigtry.com/api/status to confirm it is platform-side, not you. |
| Output is generic or misses the point | The input lacked specifics or had competing instructions | Add audience + goal + one concrete detail to the brief and regenerate. Do not start from scratch — iterate. |
| You are out of free uses | The daily free allowance for this tool is spent | Wait for the midnight reset (your local time), or add a credit pack / subscription — every tool shows its exact cost up front. |
| The page seems frozen mid-generation | A network hiccup or long video render | Reload the page and generate again — nothing is charged unless the generation completes. |
| Video render is taking long | Video is the heaviest generation type | Keep the tab open up to 5 minutes; test with a short clip first to confirm the pipeline is live. |
| A scheduled post failed | Expired or revoked platform token, or a platform outage | Reconnect the platform in the automation area — one failing network never blocks the other ten. |
| API returns 401 | Key revoked, mistyped, or missing from the Authorization header | Send the key as `Authorization: Bearer gt_live_…`. Create a new key in the dashboard if the old one was revoked. |
| API returns 403 | The key lacks the required scope (for example tools:execute) | Edit the key in the dashboard and add the scope, or create a new key with it. |
| API returns 429 | Per-key rate limit reached | Respect the Retry-After header, then retry. Limits are per key — spread load across keys only if your plan allows. |
| API returns 503 with attempts[] | All AI providers were temporarily unreachable | The error is honest, not silent corruption. Retry with backoff; the attempts[] array tells you exactly which providers failed and why. |
| Login or signup email not arriving | Mail delayed or filtered | Check spam, then request a new code. Adding your work domain to your allowlist prevents recurrence. |
| A tool you remember is missing | The catalog evolves; slugs occasionally merge | Search the /tools hub by intent ("write a …") — the search finds tools by what they do, not just by name. |
How do I check whether the problem is on my side?
Open gigtry.com/api/status — a public, real-time system status endpoint. It reports whether the website, AI generation, auto-posting pipeline and public API are operating normally, in plain language, updated every minute. If status is operational and your generation still fails, the cause is almost always input- or credit-related, and the table above covers both. If status is degraded, the fix is simply to retry in a few minutes — degraded states self-heal as provider capacity returns.
The iterate loop that fixes "bad output"
Regenerate with one added constraint at a time — "shorter", "more formal", "add a real example", "under 150 words". Each loop keeps what worked and fixes one thing. This beats rewriting the prompt from scratch every time, and it is how the platform's own editors refine content.
When should you actually contact support?
Rarely — and only for account-specific matters the self-service layer cannot see: billing disputes, the student/nonprofit discount activation, or data deletion requests under the privacy policy. Everything operational — generation, scheduling, API keys, credits, publishing — is designed to be diagnosable and fixable by you alone, which is why most users never need the support inbox at support@gigtry.com.
Frequently asked questions
Why did my generation fail with a "busy" error?
The free AI capacity pool was momentarily saturated and the platform queues honestly rather than pretending success. Wait about 30 seconds and retry — requests automatically fall back across providers, so transient failures usually clear on the second attempt.
How do I know if GigTry is down right now?
Open gigtry.com/api/status. It is a public status endpoint with real-time plain-language health for the website, AI generation, auto-posting and the public API — the same check support agents would run first.
My API key stopped working — what do I do?
Check the status code: 401 means the key is missing, mistyped or revoked (send it as a Bearer token or create a new key); 403 means the key lacks the scope your call needs (add tools:execute for execution); 429 means rate limiting (honor Retry-After). All are fixable from the dashboard without support.
A scheduled social post failed to publish — is my account broken?
Usually the platform token expired or that one platform had an outage. Reconnect the platform from the automation area and requeue the item — results are per-platform by design, so the other nine networks were unaffected.
I was charged a credit but saw no output — what now?
You are not charged unless a generation completes; a reload and retry is always safe. If you ever see a charge without output, note the tool and timestamp and write to support@gigtry.com — it will be refunded.
Related guides
What Is GigTry? Complete Platform Overview
GigTry is an all-in-one AI platform: 89 tools for writing, images, video, SEO and code, plus social auto-posting, a public API and a freelancer marketplace.
Getting Started with GigTry: Your First Generation in 2 Minutes
Step-by-step guide: create your free account, pick a tool, run your first AI generation, and understand credits — most users finish their first output in under two minutes.
The 10-Minute Setup Checklist: From Sign-Up to First Published Post
A complete self-service checklist: create your account, run your first tool, understand credits, schedule your first post and connect the API — no support contact needed.
Was this guide what you needed?