Skip to main content
Announcements
A fresh, new look for the Data Integration & Quality forums and navigation! Read more about what's changed.
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

[resolved] Job's icon with red cross without error on running in 3.1.3

Hello,
I was on 3.1.2 version and my job was working good.
I use now the 3.1.3 version (I am using the same workspace that I used for 3.1.2), and just after runing my job the red cross that indicate I have an error appear on the job's icon but I don't have error on the log window.
My Job contains subjobs, a tFileInputPositional, a tMap, a tContextLoad and a tFileArchive.
It's not a problem for me because the job ended correctly, but it could be a bug.
Regards.
Labels (2)
16 Replies
Anonymous
Not applicable
Author

hi,
use the same workspace it's not the good way to migrate for one version to another.
it's not a good idea at all in fact.
use  import/export function or create new projet & import from existing project.
you've got differents things to do if you're sharing project on svn .
regards
laurent
Anonymous
Not applicable
Author

Hi Bogdan,
The same thing happened to me as well. I am on version 5.4.2 (paid version) of Talend and it is still an issue unsolved.
Your suggestion, sarah_qureshi,  works for only a few seconds. The red cross reappears after you close the job.
I have created a Ticket to Talend Support. I will post here if I receive any information regarding a solution.

Could you please give us more information about your current situation?
Best regards
Sabrina
Anonymous
Not applicable
Author

about red cross on supposed failing job, it's an old graphic bug. Sometimes, close and reopen the job correct it . sometimes ... not 0683p000009MACn.png
to be honest it's none impact graphic bug that I don't care 0683p000009MA9p.png
regards
bogdan_popescu
Contributor

I can tell you that sometimes when I develop and test the job, if it is broken, the red cross appears and it stays like this even if I correct it and rerun the job. It has nothing to what I develope (simple or complex). It is only an interface error in my opinion, like kzone tells.
And I fully agree with "Sometimes, close and reopen the job correct it . sometimes ... not ". It is 100% true. Graphic error. Now it is good to know all these and I hope it will be helpful for others too.
Anonymous
Not applicable
Author

Hi bogdan.popescu,
Thanks for your feedback.
Best regards
Sabrina
juanhdv
Contributor

Hello

I am getting same issue with version 7.3.1. This issue has been living with us at least 11 year.

Anonymous
Not applicable
Author

Hello,

Sorry for the inconvenience. It would be great if you could share your own scenario with us and we will try our best to make it.

Best regards

Sabrina