Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Got a problem?

1. Search using the upper-right search box, e.g. using the error message.
2. Do you think FireCloud might be down? Please read this before posting.
3. Be as detailed as you can when describing your problem, i.e. tell us what happened or didn't happen rather than "it didn't work" or "it failed".
4. Include the full text of any error messages you encounter.
5. Include screenshots to show any abnormal display or indicators.
6. If the problem affects a workspace, use the Share button in FireCloud to share it with [email protected] Provide the name of the workspace as well as any submission and workflow identifiers in a forum post. By sharing with this group, you are giving access to the Data Sciences Platform's communication team and potentially engineers on the NCI Suitability Roster if further troubleshooting is required. Please consider whether your data is sensitive and should be shared with these individuals. If you have an Authorization Domain set, this group will not have access to the contents of the workspace even after sharing.

Get notifications!

You can opt in to receive email notifications, for example when your questions get answered or when there are new announcements, by following the instructions given here.

Formatting tip!

Wrap blocks of code, error messages and BAM/VCF snippets--especially content with hashes (#)--with lines with three backticks ( ``` ) each to make a code block as demonstrated here.

Jump to another community

Latest Release: 02/19/19
Release Notes can be found here.

Error Viewing Inputs for a Task

danielr Broad InstituteMember, Broadie ✭

February 2016 in Ask the FireCloud Team

When clicking on the Inputs hyperlink for a job, I'm unable to view them and get the following error:

Uncaught TypeError: re-find must match against a string.

I don't have any Array inputs or outputs for this task. Any idea what could be the cause of this?

Thanks,
Daniel

Screen Shot 2016-02-24 at 6.09.37 PM.png 206.4K

0 ·

or Register to comment.