FFAStrans forum

Hi @emcodem,

is there some need to set correct regional settings to get rid of this error in webinterface or is this a bug?

Many thanks,
mrazik

Hey @mrazik
uhm everything should be independent of regional settings.
Does this happen only for certian jobs or all jobs?

Could you post a text file with the output of this please (just call in browser):
http://localhost:65445/api/v2/history

Hi @emcodem,

attaching the file. I see there the format - "2021-10-12T16:26:35.412+05.50"

Many thanks,
mrazik

OK i remember that particular piece of code very well... i was thinking: "do i need to make the effort and support timezones with half hours - nahhh how big is the chance that a ffastrans user lives in such a timezone". Looks like i was wrong hehe, i should have looked up timezones so i see that india and australia would be affected at least.

Can you please try this? And please have a look if the time is displayed correctly, i was not 100% sure if i need to put :50 or :30 to my time parsing function "moment".

https://drive.google.com/file/d/1EWrvEq ... sp=sharing

Hi @emcodem,

now the time is shown in running jobs! Unfortunately still missing in processed.

mrazik

yeah, the history is already stored in the database of webinterface. New jobs should have a time but the sorting might be defect because invalid times are stored.
I fear to recover completely, you got to stop webinterface, then delete webinterface/database/jobs file and start again. It will re-import all jobs that ffastrans has in history at startup and times should then be correct.

well, no new completed jobs are visible in the processed in webinterface

Even after you deleted the Jobs file?

Yes! Deleting the jobs file makes the magic! Man, I own you a beer!!!

Thank you!

Question regarding branched workflows and how they are reported in the web interface. I added a branch to my Youtube workflow to find and report the URL of the requested link. This results in the webui having two lines for the same workflow. The issue I am trying to resolve is that my tiny little branch always seems to be the parent result, so now all my jobs show they only take a few seconds to complete unless I drill down in each result. I know I could put these two nodes in series in the main success branch but I don't want them to disrupt the whole workflow if they fail for some reason. Is there some way to end a workflow branch with something like a /dev/null so its success/fail doesn't get reported at all?