FFAStrans forum

Hi guys,

I'm currently developing a custom processor node and testing various functions.

Today I had the chance to run it in a real environment with actual files, and I ran into a strange issue: my node reaches a timeout and gets forcibly aborted if job is longer than 10 minutes. I checked the “Timeout level” section in the wiki:
https://ffastrans.com/wiki/doku.php?id= ... ow%20quick

However, I couldn’t find any reference for the unit being used. Is it seconds, minutes, hours… or moons?
No matter what value I set, the job still gets aborted.

Am I missing something here?

Steipal, FranceBB, emcodem would love your thoughts on this.

Hey Aris,
welcome to the Forum and thank you for using FFAStrans!
Happy when someone uses the plugin mechanism... do you work with a Coding Assist like claude or completely manual? Just asking because i tried claude last time and the result was ok but only 95% worked out of the box.. i'd like to get to 100%...

I believe the timeout that is reached there is the node-level timeout not the job level timeout. As far as i know all these timeouts are minutes. For plugin processors this should be defined in node.json
"timeout_minutes": 120,

Let me know if this helps?

Hi emcodem,

Thanks for your reply. Fortunately, it was indeed the "timeout_minutes" setting in node.json.
I set up node.json once and never looked back, so I was almost sure the issue was coming from the job itself.

As this is my second plugin, but the first one to be released, yes, I tried Codex. I'm really impressed with it.
The other plugin was coded manually, with some assistance from ChatGPT for a few questions I had.
It worked well, but it's not quite the same experience as working with an agent.

Thanks!

Great, thanks a lot for letting me know. I'll do my best to support the agentic workflow, the goal is you just tell your vision and the docs link to plugin proc and you get a good result on first try. The current documentation does not seem to be 100% accurate to support this...