LlamaGen support and project best practices
Keep projects recoverable, make focused changes, and preserve the evidence needed to resolve a problem.
Protect useful work
- Keep the project URL and project or artwork ID.
- Download approved deliverables before large revisions.
- Use a branch, copy, Generation history, or Version history when the active workspace provides it.
- Change one variable at a time when testing prompts, references, or models.
- Redraw the affected panel instead of regenerating an accepted project.
Make results easier to review
- Keep canonical character descriptions short and stable.
- Separate identity details from temporary pose, emotion, and scene details.
- Proofread text outside the image-generation step when possible.
- Review every page at final size and in the intended reading order.
- Open downloaded files outside LlamaGen before delivery.
When an operation fails
Check service status, preserve the exact error, and avoid repeated paid retries while the operation state is unknown. Use the Troubleshooting section for the specific symptom.
Keep support reports privacy-safe
Include IDs, steps, timestamps, environment, and redacted screenshots. Never send passwords, live sign-in links, session cookies, API keys, or full payment card information.
Was this article helpful?
How LlamaGen Verifies AI Comic Results
Learn how LlamaGen defines first delivery, revisions, acceptance, timing, cost, limitations, downloadable artifacts, and evidence hashes.
LlamaGen for teams, education, and enterprise
Prepare requirements for team workflows, APIs, security review, purchasing, and support without assuming unconfirmed availability.