Troubleshooting
A known part number is not found
Check that the identifier is complete and resembles BBa_B0034. Remove spaces
and try the exact part number rather than descriptive text.
You can also open the Registry directly to confirm that the record is published and available.
Search results seem unrelated
Descriptive searches can match text inside part descriptions. Use a complete part number for exact lookup, or make the search phrase more specific.
Always review the part number, biological role, description, and sequence before importing.
The Registry part page is temporarily unavailable
The iGEM Registry is an external service. A timeout or unavailable response does not modify your local data. Retry the page later.
If other Registry parts load but one record does not, the source record may contain incomplete or newly introduced metadata. Report the part number and time of the error to your FlaskTrack administrator.
A source or annotation field is blank
Registry records vary in completeness. FlaskTrack displays fields that the Registry provides and treats unavailable optional text as blank. Use the Registry source, design, and experience pages for additional context.
I cannot import a part
Confirm that:
- you are working inside an organization;
- your role has permission to create records;
- the Registry part still loads; and
- the record has a valid Registry identifier.
If the same part was already imported, FlaskTrack refreshes the existing organization record rather than creating a duplicate.
My local record is missing from verification
The verification list includes available imported biological parts, plasmids, and Molecular Studio sequences in your organization. Confirm that the record:
- belongs to the current organization;
- has not been deleted; and
- appears in the applicable Molecular Studio or plasmid catalog view.
The selector says “no released sequence”
For a plasmid, release or publish the intended Molecular Studio sequence to the plasmid catalog so the plasmid has a synchronized sequence snapshot.
For a genetic construct, confirm that it has a current sequence version in the Sequence Library.
Then return to Registry verification and run the comparison again.
An expected plasmid match reports a mismatch
Check for:
- a different plasmid backbone;
- additional promoters, terminators, tags, linkers, adapters, scars, or assembly junctions;
- a partial Registry part being compared with a complete construct;
- a local working version being compared instead of the intended released record;
- ambiguous or unsupported bases; or
- a genuine sequence change.
Circular-origin and reverse-complement equivalence are checked automatically. If FlaskTrack still reports a mismatch, the complete sequences differ.
Metadata refresh did not change my description
Refresh does not overwrite non-empty local descriptions. This is intentional: your organization's curated description takes precedence over external metadata.
The latest Registry description remains preserved in the external metadata snapshot.
A previous result changed after verification was run again
The linked-record table shows the most recent result. Earlier comparisons remain in the append-only verification-event history with their original timestamps and sequence digests.
Possible causes include:
- a new current Molecular Studio sequence version;
- a newly released plasmid sequence;
- selecting a different Registry part; or
- an updated Registry sequence.
Review both sequence histories before deciding which result applies to your laboratory work.
Information to include when reporting a problem
Provide your administrator with:
- the Registry part number;
- the local record name and type;
- the action you attempted;
- the displayed error message;
- the approximate time; and
- whether other Registry records were working.
Do not include proprietary DNA sequences in an external support request unless your organization's data-handling policy permits it.