Orchestration Job fails to call Transformation Job

We have some Orchestration Jobs that get stuck in a call to a Transformation Job.

 

Only way to stop it is Ctrl+ "Cancel and Continue".

 

We found a workaround that is to rename the Transformation Job to a different name.

 

I compared the code of the Orchestration Job and only the name of the Transformation Job being called is what changes.

 

This happens from time to time over the last couple of months without apparent reason.

 

Anyone has the same issue? Any idea what may be producing this?

It looks like a bug but I am not sure Matillion can investigate without a way of reproducing the bug.

Hi @FernandoHidalgoMarchione​ and and welcome!

If you think you're experiencing a bug and you've not already done so, could you please send in a Support ticket to the team via our Support site here. That way we'll be able to investigate and help you further.

Many thanks,

Claire

Thanks Claire,

 

No, I haven't done it yet although I understand our Matillion support team did it.

 

I will report it anyway.