FFAStrans forum

Hi.

Found a bug - on version 1.3.0.2, 1.3.0.1

When make node "monitor - ftp" from Avid AirSpeed - it's copy(localize) files to shared\local media cache and stop, any next node(encode, delivery, etc.) ignored.

on version 1.3, 1.2.2.1 - there are no this bug


Is it possible to fix it localy? Or only whait next update?

thx.

Cant reproduce on 1.3.0.2, Can you please share the full_log.json of a failing job and also share your workflow?

i chacked at five different serv. & pc to two differen AirSpeed's - and it was all the same, only 1.3 work.
Attachment delete

Hi,

thanks for the files, unfortunately missing full_log.json of a failed job.. Do you even see a job in the ffastrans jobmonitor or on webinterface?

Yes,its shows in bouthe status monitor and webinterface, and it even says "The operation completed successfully"

1.3 log
Attachment delete


1.3.0.2 log
Attachment delete

Hi artjuice,

Thanks for the bug report and logs. I think I know what's wrong and it's related to some changes made for 1.3.0.1 so the bug seem valid. However, you should be able to come around it by setting the next node to execute on "Both" rather then "Success". Can you please try that and report back? In the mean time I will fix the issure for the next release.

EIDT: Can you also please replace your current processors.a3x with the one attached and run the job again without setting next node to execute on "Both"?

-steinar

Hi
v. 1.3.0.2:
First, i set execute on "Both" - its Ok.
Then i replace with new processors.a3x, set execute on "Success" - its Ok!

Great! Thanks for testing and reporting back

-steinar

admin wrote: ↑Tue Mar 28, 2023 7:52 pm Great! Thanks for testing and reporting back

-steinar

Hi.
After a few days of work i saw that some files have status "success" but they wheight 0, after restart such files it's says "status":"(99\/100 retries) Getting error code 6 - The handle is invalid, when trying to deliver"

When i changed to execute on "Both" - such files was delivered from first try.
I think bug is still present.

Hi again artjuice,

I think this is another bug I've been chasing for a while and yesterday I think I finally cracked it. At least initial tests show good results. Hopefully 1.3.1 will be out very soon.

-steinar