Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
MattE
Creator II
Creator II

subjob cannot be resolved to a type

This keeps happening to me all the time in different versions of Studio and in different project, on different machines so must be a problem with studio.

I create a job which has other tRunJobs inside it. It works fine. Then one day I'll open the same job and there are errors in the code tab saying that jobname cannot be resolved to a type

The fix is to then click on the component>Component Tab and repoint it to the job in the repo browser.

Very tedious.

Any one any idea why this keeps happening?

Labels (3)
2 Replies
Anonymous
Not applicable

Hi @Matt Evans​,

 

I have seen this a couple of times myself. However, it has usually been in projects that have other issues. I have not seen it since I have been using v7. You are right, this is frustrating when it happens. To get to the bottom of why this is happening in your projects, it would be good to take a look at a project where this is happening. I see from some of your other posts that you are using Talend Cloud. This suggests that you (or the company you are working for) have a contract. Would you mind raising a Support call about this the very next time it happens?

 

As I said, I have seen this before, but not recently and I have had a few goes at reproducing this since you raised this. Without success (or without failure as it were). I know this is not the answer you were looking for, but I am very keen to make sure we can tackle this and if you are seeing it regularly, it would be really useful to see your project to find the cause.

 

Regards

 

Richard

MattE
Creator II
Creator II
Author

Yes no problem I'll raise a ticket the next time it occurs. As you said, when i fixed this issue it uncovered another one (a missing context value in a subjob) so perhaps this error is a red herring. I'll confirm the next time it happens.