Publish to TMC succeeds but nothing is there

[MattE]

Hey, We've just upgraded to Studio v8 and have republished all our existing jobs. They have all published and ran in the cloud successfully except for 1 job. For this job, the publish process completes with the success message but there is nothing in TMC or on the server so it hasn't worked, however, there are no errors or warnings anywhere. Furthermore this job runs fine locally in studio and i can do a build to my local machine again, without any errors so something is going wrong on the journey to the cloud.

Any ideas?

Studio 8 R2024-11v2

Thanks

[MattE]

note this behaviour is replicated across 3 other people.

[Xiaodi_Shi]

Hello @MattE 

How do you set up debug logging in TMC? Is the Log Level = DEBUG? (Debug is only visible on a previous execution). If you could not directly trigger in debug and use the manual debug mode from a previous execution, could you please try to use the custom logging configuration that is defined in Talend Studio?

https://help.qlik.com/talend/en-US/remote-engine-user-guide-windows/Cloud/enabling-custom-logging

[MattE]

Hi, the job does not update into TMC so i am unable to run it as debug in TMC. It does run locally on my machine fine without any errors. 

[quentin-vigne · Accepted solution]

When you publish the job, are you publishing it to the right Workspace ? (not a Personal workspace)

Have you checked everywhere on the TMC ?

Under management look under the category "Artifacts" maybe it's here and not present as a task if there is any conflict in names.

If you can, create any new job with only a tjava component doing a print and try to publish it, to see if it succeed or not.

If all else fails, gather logs from Studio and TMC, along with details of the problematic job, and reach out to Talend support. Provide them with:

• A summary of the issue.
• Logs from both Studio and TMC.
• Details of the job and environment configuration.

They'll be able to see what's happening

[MattE]

Thanks, it IS in artifacts even though this was a very old job which has been running for years and has never had the name changed. Do you know why this would end up in artifacts and not just update the existing task in TMC?

[quentin-vigne]

The main reasons could be that your task is not setup as "Always use the latest available artifact version" which would prevent the task to automatically update :

Go to your task, edit the configuration and select the Artifact version you want to use