62 List of j5 error messages j5 input file specific error messages: Combinatorial target part order list file: Can't open file file_name: error_message j5 is unable to open the combinatorial target part order list file file_name. Check to make sure that file_name matches the name of a combinatorial target part order list file in the current working directory (if calling j5 from the command line), or that you specified a combinatorial target part order list file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. Combinatorial target part order list file: part_name appears to be a part name, but it appears in the list before any combinatorial bin. Either correct this, or if you intended to design a single construct, please use j5's "Mock Assembly", "SLIC/Gibson/CPEC Assembly" or "Golden-gate Assembly" design option instead of "Combinatorial Mock Assembly", "Combinatorial SLIC/Gibson/CPEC Assembly" or "Combinatorial Golden-gate Assembly" design. The name of a part, part_name, in the combinatorial target part order list file appears before the definition of a combinatorial bin. This message is generated during combinatorial construct assembly design. Perhaps you intended to design a single construct Mock Assembly, SLIC/Gibson/CPEC/SLiCE or Golden-gate assembly instead? Combinatorial target part order list file: target bin bin_number ("bin_name"), contains no parts. Exiting... The target bin bin_number (whose name is bin_name) contains no target parts. Downstream automation parameters file: Can't open file file_name: error_message j5 is unable to open the downstream automation parameters file file_name. Check to make sure that file_name matches the name of a downstream automation parameters file in the current working directory (if calling j5 from the command line), or that you specified a j5 parameters file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. Genbank sequence file file_name has feature feature_line whose start bp (start_position) exceeds the length of the sequence (sequence_length) One of the Genbank files attempted to be input into j5 (namely file_name) has a non-sense feature whose start bp position is greater than the total length of the sequence. Please check and modify this Genbank file for correctness, so that no feature locations exceed the length of the sequence. j5 assembly file: Can't open file file_name: error_message j5 is unable to open the j5 assembly file file_name. Check to make sure that file_name matches the name of a j5 assembly file in the current working directory (if calling j5 from the command line), or that you specified a j5 assembly file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. j5 parameters file: Can't open file file_name: error_message j5 is unable to open the j5 parameters file file_name. Check to make sure that file_name matches the name of a j5 parameters file in the current working directory (if calling j5 from the command line), or that you specified a j5 parameters file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. j5 parameters file: the specified type IIs endonuclease recognition sequence (GOLDENGATERECOGNITIONSEQ, "golden_gate_recognition_sequence") is not found within the specified sequence to be added to the termini of each Golden Gate assembly piece (GOLDENGATETERMINIEXTRASEQ "golden_gate_termini_extra_sequence"). The specified type IIs endonuclease recognition sequence golden_gate_recognition_sequence (e.g. GGTCTC for BsaI) is not contained within the golden gate termini extra sequence golden_gate_termini_extra_sequence (e.g. CACACCAGGTCTCA). Perhaps you changed the golden gate recognition sequence for a different type IIs endonuclease (e.g. for BsmBI, to CGTCTC), but forgot to make the corresponding changes to the golden gate termini extra sequence (e.g. for BsmBI, to CACACCACGTCTCA)? Master direct syntheses list file: Can't open file file_name: error_message j5 is unable to open the master direct syntheses list file file_name. Check to make sure that file_name matches the name of a master direct syntheses list file in the current working directory (if calling j5 from the command line), or that you specified a master direct syntheses list file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. Master oligos list file: Can't open file file_name: error_message j5 is unable to open the master oligos list file file_name. Check to make sure that file_name matches the name of a master oligos list file in the current working directory (if calling j5 from the command line), or that you specified a master oligos list file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. Master plasmids list file: Can't open file file_name: error_message j5 is unable to open the master plasmids list file file_name. Check to make sure that file_name matches the name of a master plasmids list file in the current working directory (if calling j5 from the command line), or that you specified a master plasmids list file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. Multi-well plate file: Can't open file file_name: error_message j5 is unable to open the multi-well plate file file_name. Check to make sure that file_name matches the name of a multi-well plate file in the zipped source plates file. The error message may provide additional information. One or more j5 input files not specified for upload or last-updated selected for re-use Check to make sure that you either specified all input files for upload (or selected to re-use the last updated versions) when using the stand alone simplified web-page interface for j5. Parts list file: Can't open file file_name: error_message j5 is unable to open the parts list file file_name. Check to make sure that file_name matches the name of a parts list file in the current working directory (if calling j5 from the command line), or that you specified a parts list file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. Parts list file: Definition of part part_name: Sequence display ID sequence_display_ID does not match a sequence contained within the sequence files listed in the sequences list file. In the parts list file, in the row defining the part part_name, the sequence display ID does not match that of any of the sequences contained in the sequence files listed in the sequences list file. Note that the sequence display ID (the text that immediately follows the ">" character in FASTA files or the first field on the "LOCUS" line in Genbank files) is not necessarily the same as the name of the sequence file that contains the sequence. To check the sequence display ID for a given sequence file, open he sequence file with a text editor (such as notepad or TextEdit). Parts list file: Two parts have the same name: part_name In the parts list file, two or more parts have the same name (part_name). Make sure that each defined part has a unique name. Sequences list file: Can't open file file_name: error_message j5 is unable to open the sequences list file file_name. Check to make sure that file_name matches the name of a sequences list file in the current working directory (if calling j5 from the command line), or that you specified a sequences list file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. Sequences list file: Sequence file type must be "FASTA" or "Genbank". file_format is not a valid file format In the sequences list file, the sequence file format must be either "FASTA" or "Genbank". Sequences list file: Two sequences have the same sequence display ID: sequence_display_ID The sequence display IDs (the text that immediately follows the ">" character in FASTA files or the first field on the "LOCUS" line in Genbank files) of two or more sequences is identical. Note that two sequence files with distinct file names can contain sequences with identical display IDs. Open the each of the sequence files listed in the sequences list file with a text editor (such as notepad or TextEdit), and check to see which the files contain sequences with identical display IDs (e.g. sequence_display_ID), and make sure that each sequence has a unique display ID. Source plates list file: Can't open file file_name: error_message j5 is unable to open the source plates list file file_name. Check to make sure that file_name matches the name of a source plates list file in the current working directory (if calling j5 from the command line), or that you specified a source plates list file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. Target part order list file: Can't open file file_name: error_message j5 is unable to open the target part order list file file_name. Check to make sure that file_name matches the name of a target part order list file in the current working directory (if calling j5 from the command line), or that you specified a target part order list file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. Target part order list file: part_name appears to be a combinatorial bin name. Please use j5's "Combinatorial SLIC/Gibson/CPEC Assembly" or "Combinatorial Golden-gate Assembly" design option instead of single construct "SLIC/Gibson/CPEC" or "Golden-gate Assembly" design. The name of a part, part_name, in the target part order list file begins with the character '>', which is used to designate a combinatorial bin name during the combinatorial SLIC/Gibson/CPEC/SLiCE or Golden Gate design process (see the target part order list input file documentation for more information). This message is generated during single construct SLIC/Gibson/CPEC/SLiCE or Golden-gate assembly design. Perhaps you intended to design a Combinatorial SLIC/Gibson/CPEC/SLiCE or Golden-gate assembly instead? Target part order list file: part_name not found in the parts list The part part_name in the target part order list file is not defined within the parts list file. Check to make sure that the part name in the target part order list file exactly matches that in the parts list file. Target part order list file: DIGEST forced assembly strategy may only be set for the first target part Only the first part in the target part order list file may be forced to use the "DIGEST" assembly strategy. Target part order list file: forced_assembly_strategy is not a recognized forced assembly strategy The only allowable options for forced assembly strategies are "DIGEST", "PCR", "Direct Synthesis", "Embed_in_primer_forward", "Embed_in_primer_reverse", "unspecified", and empty. Zipped sequences file: sequence file sequence_file_name not found within the zip_file_name zip file j5 is unable find the sequence file sequence_file_name that is listed in the sequences list file within the zipped sequences file zip_file_name. Check to make sure that sequence_file_name is contained within the zip file. SLIC/Gibson/CPEC/SLiCE or Golden Gate specific error messages (for general assistance see the SLIC/Gibson/CPEC/SLiCE or the Golden-gate description sections): Eugene design rules not satisfied, aborting assembly design: error_message Before an SLIC/Gibson/CPEC/SLiCE or Golden Gate assembly is designed, j5 checks whether or not the Eugene design rules are satisfied for the construct to be assembled. If one or more rules is violated, the assembly design is aborted and the error message may provide additional information. Overhang/Overlap design: assembly junction junction_number (between assembly pieces 5'_piece and 3'_piece) is overconstrained. Need a constant OVERHANGOVERLAPBPS bps region for the overhang/overlap, but only have available_overhang_overlap_bps bps. j5 requires a sequence region bordering or containing assembly junction junction_number that is at least OVERHANGOVERLAPBPS bps in length (e.g. 4 bp) that will be exactly the same in all resulting assembled sequences in order to select an overhang/overlap sequence. If no such constant sequence region exists, then it will not be possible to design a scar-less SLIC/Gibson/CPEC/SLiCE or Golden Gate combinatorial assembly. Your options to address this include limiting the parts that will be included in the assembly of the combinatorial library, until a constant sequence region is achieved, or by purposely introducing a constant sequence region (introducing scars in the process) by adding constant bps (or making constant point mutations) to the ends of the assembly pieces (5'_piece and 3'_piece) at assembly junction junction_number. Overhang/Overlap design: forced overhang/overlap for assembly junction junction_number (between assembly pieces 5'_piece and 3'_piece, overhang_overlap_sequence) and the forced overhang/overlap for assembly junction junction_number_2 (between assembly pieces 5'_piece_2 and 3'_piece_2, overhang_overlap_sequence_2) are incompatible: error_message You have selected to force the overhang positions for assembly junctions junction_number and junction_number_2 as part of a SLIC/Gibson/CPEC/SLiCE or Golden Gate assembly process, but the resulting overhang/overlap sequences (overhang_overlap_sequence, and overhang_overlap_sequence_2) are incompatible, meaning that they will base pair with each other to an extent greater than that which is tolerable (by default, more than 2 out of the 4 bp are self-complementary for Golden Gate; this parameter is adjustable in the j5 parameters file). The error message may provide additional information. Overhang/Overlap design: forced overhang/overlap for assembly junction junction_number (between assembly pieces 5'_piece and 3'_piece, overhang_overlap_sequence) is self-incompatible: error_message You have selected to force the overhang/overlap position for assembly junction junction_number as part of a SLIC/Gibson/CPEC/SLiCE or Golden Gate assembly process, but the resulting overhang/overlap sequence (overhang_overlap_sequence) is self-incompatible, meaning that it will base pair with itself to an extent greater than that which is tolerable (by default, more than 2 out of the 4 bp are self-complementary for Golden Gate; this parameter is adjustable in the j5 parameters file). The error message may provide additional information. Overhang design: forced overhang for assembly junction junction_number (between assembly pieces 5'_piece and 3'_piece, overhang_sequence) is incompatible with an internal overhang: error_message You have selected to force the overhang position for assembly junction junction_number as part of a Golden Gate assembly process, but the resulting overhang sequence (overhang_sequence) is incompatible with an overhang resulting from the cleavage of a Golden Gate type IIs endonuclease site internal to one or more assembly pieces, meaning that it will base pair with the internal overhang to an extent greater than that which is tolerable (by default, more than 2 out of the 4 bp are self-complementary for Golden Gate; this parameter is adjustable in the j5 parameters file). The error message may provide additional information. Overhang/Overlap design: forced relative overhang/overlap position (forced_relative_overhang_overlap_position) for assembly junction junction_number (between assembly pieces 5'_piece and 3'_piece) would result in an overhang/overlap that extends beyond the region of assembly junction sequence identity conserved over all desired combinations. In order to minimize the number of oligos required for a combinatorial SLIC/Gibson/CPEC/SLiCE or Golden Gate assembly (i.e. to maximally re-use PCR products and minimize the number of PCR products required), j5 requires that overhangs/overlaps are located about the assembly junctions such that all base-pairs that the overhangs/overlaps span are absolutely conserved across all desired combinations. This error will only occur when a forced relative overhang position is specified for a junction. For more information, refer to the Brief survey of j5 functionality documentation, concerning "when j5 designs a combinatorial Golden Gate assembly, the overhang search space about a given combinatorial assembly junction is constrained". Overhang/Overlap design: no compatible set of overhangs/overlaps is available. j5 exhaustively searches through all possible combinations of available overhangs/overlaps for the assembly junctions. Occasionally (usually only if there are many junctions and the sequence regions around the junctions from which to select overhangs/overlaps are highly constrained), it is possible that j5 can not find a set of overhangs/overlaps that are compatible with themselves and with each other. If you receive this error, it will be necessary to introduce additional scar base-pairs at one or more assembly junctions, to increase the number and diversity of the overhangs/overlaps from which to select. SLIC/Gibson/CPEC/SLiCE specific error messages (for general assistance see the SLIC/Gibson/CPEC/SLiCE description section): SLIC/Gibson/CPEC design: Digest linearized vector backbone part_name is not at least a Gibson overlap (GIBSONOVERLAPBPS bps) long When digest linearizing the vector backbone (which precludes the possibility of adding any flanking sequence), the vector backbone sequence itself must be at least a Gibson overlap long (26 bp is the j5 default; if you set an alternative length using the j5 parameters input file, GIBSONOVERLAPBPS will reflect your chosen length). It seems unlikely that one would ever digest linearize a vector backbone that isn't at least a Gibson overlap long, but j5 checks just in case. SLIC/Gibson/CPEC design: forced extra (5' or 3') CPEC overlap bps for assembly piece assembly_piece results in an overlap that is too short The extra (5' or 3') CPEC overlap bps setting specified in the target part order list file for assembly piece assembly_piece is forcing j5 to design an overlap sequence that is shorter than the minimum overlap length specified in the j5 parameters file. This can occur if the (5' or 3') CPEC overlap bps setting for assembly piece assembly_piece is too negative, and there isn't enough space on the other side of the overlap in which to expand (for example, because of a degenerate base pair or the end of sequence identity among all combinatorial variants), or the other side of the overlap is also fixed by a (3' or 5') CPEC overlap bps setting for the (subsequent or previous) assembly piece. SLIC/Gibson/CPEC design: forced extra (5' or 3') CPEC overlap bps for assembly piece assembly_piece results in an overlap that extends beyond allowable region The extra (5' or 3') CPEC overlap bps setting specified in the target part order list file for assembly piece assembly_piece is forcing j5 to design an overlap sequence that extends beyond the allowable region for the overlap (which can be constrained by a degenerate base pair or the end of sequence identity among all combinatorial variants). This can occur if the (5' or 3') CPEC overlap bps setting for assembly piece assembly_piece is too positive and there isn't enough space in which to expand, or the other side of the overlap is fixed by a negative (3' or 5') CPEC overlap bps setting for the (subsequent or previous) assembly piece. Condense multiple j5 assembly files specific error messages: Assembly file file_name header: header_line not recognized j5 expects that the first line of a j5 assembly CSV file is formatted in a particular way, so that it can tell what type of an assembly file it is dealing with. The first line of an assembly CSV file should begin with either "SLIC/Gibson/CPEC" (for a SLIC/Gibson/CPEC/SLiCE assembly file), "Golden Gate" (for a Golden Gate assembly file), "Combinatorial SLIC/Gibson/CPEC" (for a combinatorial SLIC/Gibson/CPEC/SLiCE assembly file), "Combinatorial Golden Gate" (for a combinatorial Golden-gate assembly file) or "Condensed" (for a condensed assembly file). The first line of assembly file file_name (header_line) does not match this format. Check to make sure that assembly file file_name is a proper j5 assembly CSV file. Assembly files to condense list file: Can't open file file_name: error_message j5 is unable to open the assembly files to condense list file file_name. Check to make sure that file_name matches the name of an assembly files to condense list file in the current working directory (if calling j5 from the command line), or that you specified an assembly files to condense list file to upload (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. Assembly file to condense: Can't open file file_name: error_message j5 is unable to open the assembly file file_name that is listed in the assembly files to condense list file. Check to make sure that file_name matches the name of an assembly file in the current working directory (if calling j5 from the command line), or that this assembly file is included in the zipped assembly files file (if using the stand alone simplified web-page interface for j5). The error message may provide additional information. Distribute PCR Reactions specific error messages: Multi-well plate: Error: can't find a well containing purely content_type with at least min_volume uL available in any of the plates. This error arises when searching through all of the source multi-well plates for a well that contains at least min_volume uL of available pure content_type, and not being able to find such a well. This might happen, for example, if not enough of a particular PCR template is available to distribute to all of the PCR reactions that use it. One solution is to add more pure content_type to an another (empty) source plate well. Multi-well plate: plate plate_ID well plate_well is too full to add an additional volume uL of liquid. This error arises when attempting to add an additional volume uL of liquid to well plate_well in plate plate_ID when this additional volume would exceed the well's maximum capacity. Check the downstream automation parameters file to make sure that the maximum well capacity volume is what you intended, and that the multi-well plate files don't over allocate liquids to the well plate_well in plate plate_ID. File and/or directory read/write access permission related error messages: If you encounter one of the following errors when running j5 from the command line, it is most likely because file and directory permissions in the current working directory prevent j5 from creating new or editing existing files. If you encounter one of the following errors when using j5 with the stand alone simplified web-based interface, it is most likely due to an improperly installed local version of the j5 stand alone simplified web-based interface (contact your IT support staff and/or consult the local installation of j5 documentation page for more information). Can't change directory back to the parental directory j5 is unable to change the directory back to the parental directory. Can't change working directory to directory_name: error_message j5 is unable to change the working directory to directory_name. The error message may provide additional information. Can't copy file file_name back to the parental directory j5 is unable to copy the file file_name to its parental directory. Can't copy file file_name to the upload directory j5 is unable to copy the file file_name to the upload directory. Can't copy j5 input file file_name to directory directory_name: error_message j5 is unable to copy the j5 input file file_name to directory directory_name. The error message may provide additional information. Can't create directory directory_name: error_message j5 is unable to create the directory directory_name. The error message may provide additional information. Can't extract zipped sequence file file_name to directory directory_name: error_message j5 is unable to extract the zipped sequence file file_name to directory directory_name. The error message may provide additional information. Can't open file file_name for writing: error_message j5 is unable to create the file file_name. The error message may provide additional information. Can't remove directory directory_name: error_message j5 is unable to remove the directory directory_name. The error message may provide additional information. Can't zip j5 working directory directory_name j5 is unable to zip the j5 working directory directory_name. Combinatorial assembly output file: Can't open file file_name for writing: error_message j5 is unable to create the new combinatorial assembly output file file_name. The error message may provide additional information. Condensed assembly output file: Can't open file file_name for writing: error_message j5 is unable to create the new condensed assembly output file file_name. The error message may provide additional information. Master direct syntheses list file: Can't open file file_name for appending: error_message j5 is unable to append new direct syntheses pieces to the master direct syntheses list file file_name. The error message may provide additional information. Master oligos list file: Can't open file file_name for appending: error_message j5 is unable to append new oligos to the master oligos list file file_name. The error message may provide additional information. Master plasmids list file: Can't open file file_name for appending: error_message j5 is unable to append the newly designed plasmid(s) to the master plasmids list file file_name. The error message may provide additional information. New j5 assembly file: Can't write to file file_name: error_message j5 is unable to write the new assembly file file_name. The error message may provide additional information. Local installation related error messages: If you encounter one of the following errors, it is most likely due to an improperly installed local version of the j5 package. Contact your IT support staff and/or consult the local installation of j5 documentation page for more information. Cannot use Text::CSV package: error message j5 is unable to successfully call the Text::CSV perl module to parse a comma separated value (CSV) file. Check your local installation of Text::CSV, and make sure it meets the requirements of j5. The error message may provide additional information. Primer3 executable can not be found at PRIMER3PATH j5 is unable to successfully call the Primer3 executable at the specified path PRIMER3PATH. Check your local installation of Primer3, and make sure it meets the requirements of j5. The path to Primer3 is specified in the perl module file j5/Configuration.pm. Command-line interface error messages: If you encounter one of the following errors, it is most likely due to specifying too many or too few j5 input files on the command line. Usage: j5_program j5ParametersFileName SequencesListFileName PartsListFileName TargetPartOrderListFileName MasterPlasmidsListFileName MasterOligosListFileName MasterDirectSynthesesListFileName The j5 perl script j5_program expects seven j5 input files to be specified on the command line (as suggested in the error message). Make sure that you have specified the correct number of input files. Four j5 perl scripts (j5_SLIC_Gibson_CPEC.pl, j5_golden_gate.pl, j5_combinatorial_SLIC_Gibson_CPEC.pl, and j5_combinatorial_golden_gate.pl) have this same command line usage. Usage: j5_program j5ParametersFileName SequencesListFileName ZippedSequencesFileName PartsListFileName TargetPartOrderListFileName MasterPlasmidsListFileName MasterOligosListFileName MasterDirectSynthesesListFileName The j5 perl script j5_program expects eight j5 input files to be specified on the command line (as suggested in the error message). Make sure that you have specified the correct number of input files. Four j5 perl scripts (j5_SLIC_Gibson_CPEC_zip.pl, j5_golden_gate_zip.pl, j5_combinatorial_SLIC_Gibson_CPEC_zip.pl, and j5_combinatorial_golden_gate_zip.pl) have this same command line usage. Usage: j5_program AssemblyFilesToCondenseFileName The j5 perl script j5_program expects one j5 input file to be specified on the command line (as suggested in the error message). Make sure that you have specified the correct number of input files. The j5 perl scripts j5_condense_assembly_files.pl has this command line usage. Usage: j5_program AssemblyFilesToCondenseFileName ZippedAssemblyFilesFileName The j5 perl script j5_program expects two j5 input files to be specified on the command line (as suggested in the error message). Make sure that you have specified the correct number of input files. The j5 perl scripts j5_condense_assembly_files_zip.pl has this command line usage. Internal error messages: If you encounter one of the following errors, it is most likely due to an internal bug within j5. Please contact the j5 development team with details so that we can fix the problem. Combinatorial design: Can't open file template assembly file file_name: error_message j5 is unable to open the combinatorial template assembly file file_name. It is likely that the template assembly design did not complete correctly. The error message may provide additional information. Combinatorial design: Can't open condensed assembly file file_name: error_message j5 is unable to open the condensed assembly file file_name that results from condensing each individual combinatorial assembly.  It is likely that condensing the individual assembly files did not complete correctly. The error message may provide additional information. Convert_Mac_Carriage_Returns: Can't open file file_name: error_message j5 is unable to open the file file_name to replace mac-style carriage returns with standard new line returns. The error message may provide additional information. Golden-gate design: 3' overhang of assembly piece upstream_piece (sequence upstream_sequence) does not match the 5' overhang of assembly piece downstream_piece (sequence downstream_sequence) j5 has erringly designed a Golden Gate assembly that results in two neighboring assembly pieces, namely upstream_piece and downstream_piece, that do not having matching Golden Gate overhangs. The overhang sequences at the ends of the two pieces, upstream_sequence and downstream_sequence, are displayed. SLIC/Gibson/CPEC design: 3' end of assembly piece this_piece does not match 5' end of assembly piece the_next_piece this_piece_3'_sequence the_next_piece_5'_sequence j5 has erringly designed a SLIC/Gibson/CPEC/SLiCE assembly that results in two neighboring assembly pieces, namely this_piece and the_next_piece, that do not having matching sequence homology overlap regions. The ends of the two sequences, this_piece_3'_sequence and the_next_piece_5'_sequence, are displayed. j5 XML-RPC web service specific error messages: j5_XML_RPC: Invalid username or password A valid username and password is required for creating a new j5 session ID. Accounts are available at the j5 website's request an account page. j5_XML_RPC: method method_name not recognized... The requested method, method_name, was not recognized. The set of implemented method names is provided on the j5 XML-RPC web services page. j5_XML_RPC: session id j5_session_id is invalid or has expired. Please use the XML-RPC method CreateNewSessionId to obtain a valid j5 session id... The session id j5_session_id passed as a parameter to the XML-RPC web service method was either invalid, or has expired. A valid session id must be used when calling the j5 XML-RPC web services. j5_XML_RPC: DesignAssembly: assembly method assembly_method is not recognized The assembly method assembly_method was not recognized when calling the XML-RPC method DesignAssembly. The set of implemented assembly methods is provided on the j5 XML-RPC web services page. j5_XML_RPC: DesignDownstreamAutomation: automation task automation_task is not recognized The automation task automation_task was not recognized when calling the XML-RPC method DesignDownstreamAutomation. The set of implemented assembly methods is provided on the j5 XML-RPC web services page.