Credits & Logs
OctoReport uses credits as the billing unit for system resources. This document explains how to obtain credits, view consumption details, use redemption codes, and view task execution logs.
[Placeholder]
Credits management page screenshot - showing current balance, acquisition records, consumption details entry
How to Obtain Credits
New User Reward
After successful registration, the system automatically grants 10,000 credits. These credits are enough for:
- Create 5-10 data sources and run for 1 week
- Generate 20-50 basic reports
- Have 100-200 Ask conversations (using small models)
Note
New user reward is granted only once upon first registration. Plan your usage wisely. It's recommended to start with small-scale data sources and simple report templates, then expand after familiarizing yourself with the system.
Redemption Code Top-up
When credits are insufficient, you can top up using redemption codes:
Top-up Steps:
- Click "Credits Management" in the left sidebar
- Click "Use Redemption Code" button
- Enter 8-16 digit redemption code (case-sensitive)
- Click "Redeem" to confirm
- Credits will be added immediately upon success
Redemption Code Notes
• Each redemption code can only be used once
• Redemption codes have expiration dates, use within validity period
• Successful redemptions generate top-up records, viewable in "Consumption Details"
• If redemption fails, check if code is correct or expired
Acquisition Records
All credit acquisition records (new user rewards, redemption code top-ups) are saved in the system and viewable on the "Credits Management" page:
- Top-up Time: When credits were obtained
- Top-up Type: SIGNUP (new user reward) or REDEMPTION (redemption code top-up)
- Top-up Amount: Number of credits obtained
- Redemption Code: If topped up via redemption code, code shown (partially hidden)
Consumption Details
Consumption Categories
| Operation Type | Cost Range | Main Factors |
|---|---|---|
| Data Collection | 1-10 credits/time | Data source type, detail scraping |
| Content Cleaning | 10-20 credits/time | Content length, LLM model |
| Report Generation | 50-500 credits/time | Number of steps, LLM model |
| Ask Conversation | 1-50 credits/time | Conversation length, LLM model |
| Trigger Inbox (Email) | 80-300 credits/time | Whether triggers report generation |
Detailed Cost Explanation
- RSS Subscription: 1-2 credits | Search Source: 2-10 credits | Web Scraping: 2-50 credits
- Content Cleaning: 10-20 credits (based on text length)
- Report Generation: 50-500 credits (based on model and number of steps)
- Ask Conversation: 1-50 credits (based on conversation length and model)
Cost Optimization Tips
• UseKEEP_OLDdeduplication strategy to avoid duplicate scraping
• For report generation, use small models in early steps, large models in final steps
• Disable unnecessary content cleaning (can trigger manually later)
• In Ask, prioritize library mode over general mode
View Consumption Records
View all consumption records on the "Credits Management" page, including: consumption time, operation type, amount, related resources, balance.
Filtering Features: By time range | By operation type | Sort by amount
[Placeholder]
Consumption details list screenshot - showing time, type, amount, balance, filtering features
Task Logs
Log Overview
Task logs record the execution status of all tasks in the system, including data collection, content cleaning, report generation, etc. Through task logs, you can:
- Understand task execution status (success/failure/in progress)
- View task execution time and duration
- Troubleshoot task failure reasons
- Monitor system health status
Log Types
| Task Type | Description | Related Resource |
|---|---|---|
| CONTENT_COLLECT | Data source content collection | Data Source (Source) |
| CONTENT_CLEAN | Content cleaning (LLM extraction) | Content |
| REPORT_GENERATE | Report generation | Report Template |
| INBOUND_REQUEST | Email trigger processing | Request Record (InboundRequest) |
Task Status
- PENDING: Task created, waiting for execution
- PROCESSING: Task currently executing
- COMPLETED: Task successfully completed
- FAILED: Task execution failed (view error information)
Viewing Logs
Click "Task Logs" in the left sidebar to view all task execution records.
Log Information: Task ID, type, status, start/end time, duration, related resources, error messages
Filtering Features: Filter by type, filter by status, sort by time, keyword search
View Task Details
Click on a task record to view detailed information:
- Data Collection: Collection count, deduplication strategy, API latency
- Report Generation: Results for each step, LLM model, token consumption
- Failed Tasks: Error type, error stack, retry count
Troubleshooting Tips: Insufficient balance requires top-up | API rate limiting reduce frequency | Network errors retry later | Other issues contact technical support
Best Practices
- Credits Management: Keep balance ≥1000 credits | Top up when below 500 | Check consumption trends weekly
- Log Monitoring: Check task status daily | Handle failed tasks promptly | Optimize tasks with excessive duration
- Cost Optimization: Use KEEP_OLD strategy | Use small models in early steps | Disable unnecessary cleaning
FAQ
1. What happens when balance is insufficient?
New tasks cannot be created, scheduled tasks are paused, historical data remains viewable, automatically resumes after top-up.
2. What to do if redemption code doesn't work?
Check if code is correct (case-sensitive), already used, or expired. Contact technical support if problem persists.
3. Task stuck in "processing" status?
Refresh page to see latest status, check error information in task details, contact technical support if over 30 minutes.
4. How to export consumption records?
Use browser print function to save as PDF, or copy table content to Excel, or contact technical support to request export.
Next Steps
- Configuration Tips - Learn how to optimize credit consumption
- Optimization & Troubleshooting - Cost optimization methods and common issue troubleshooting
- FAQ & Support - View more frequently asked questions