PlantQTLdb Assistant
Troubleshooting and Limitations
resolve missing cards, unsupported inputs, pending jobs and incomplete results
Check the returned status
Open PlantQTLdb AssistantA tool question returned only literature
State the scientific analysis and provide the required identifiers or input data. Check the returned tool status and result card; an existing completed answer is not automatically rerun.
Use the complete example, including species, identifiers or actual sequence. Questions such as 'What is STRING?' ask for an explanation rather than a network analysis.
Retry an explicit analysis
Use STRING to analyze the functional association network of Arabidopsis genes AT1G01010 and AT1G01020
what you receive
A named STRING result and, on success, its network card. If the service fails, read the returned reason instead of interpreting an ordinary literature answer as a successful network search.
A species or transcript is unavailable
- Cotton enrichment
- g:Profiler is disabled for G. hirsutum and G. arboreum; no different cotton species is silently substituted.
- Sorghum and tomato references
- Sequence extraction and the dependent gene-structure/variant-window workflow are paused pending reference compatibility checks. This does not disable every external tool for those species.
- Multiple transcripts
- Structure displays all returned transcripts. For a single extracted CDS, cDNA, protein or promoter, supply a transcript_id from the returned list.
- Mixed species or ambiguous IDs
- For a cross-species comparison, name every species explicitly and keep its identifiers and results separate. Resolve ambiguous mappings before interpreting results.
Clarifying a question and choosing a language
For a question such as 'Which genes affect drought tolerance?', include the species. A gene ID is not required when you want to discover candidates. In a follow-up, Assistant can use the species you already specified.
Assistant follows the language of your current question. You can also explicitly ask it to answer in English or Chinese; source documents do not determine the answer language.
Pending, busy and failed are different
- BLAST pending/running
- A remote job exists. Wait for the indicated interval and use Check job status, then send the composed query.
- FIMO busy
- No queued job has been created for you. Retry the request later when the single worker is available.
- Provider unavailable
- The external service did not provide a usable result. Do not read this as a biological negative.
- Answer could not complete
- Use Regenerate below the message to retry. If the request needs more information, edit it to include the species, identifiers or requested comparison. Repeated failures can be reported with the original question and time; they do not mean the database has no relevant records.
- Card loading failure
- Use Reload result when shown, or reload the conversation. A completed immutable result can be fetched without resubmitting the scientific analysis.
Empty or truncated output
A successful empty result may reflect identifier coverage, thresholds or a real lack of matching records. It is not equivalent to 'not supported' or a timeout.
Preview tables can show fewer rows than downloads. Truncation limits the data returned by the analysis itself; downloading CSV does not bypass that limit. In particular, gene-window QTL counts can be lower bounds and the associated plot can be partial.
What to include in a problem report
- The exact question, species, gene/transcript or reference version, and the displayed error/status.
- The time of the request and a screenshot of the relevant answer/card. Avoid sharing session cookies, passwords or private sequences in a public report.