-
Hello to all,
I created a job on Coconut and it failed: I was on the test plan that limits the length of the video to 1 minute and my video was 3 minutes long, so the job failed.In WordPress, FV Player Coconut correctly get the status as “error”.
Then I subscribed for a “pay-as-you-go” plan and retried the job: this time, the job was successful.
Unfortunately, it seems FV Player Coconut doesn’t updated the status in the “Jobs” section and so the job still results as failed.
I checked the notifications sent to my website and the notification about the new “success” status was correctly sent and the server correctly responded with a 200 HTTP status code.
But it seems the FV Player Coconut plugin didn’t processed it correctly as it didn’t updated the status in the jobs section.
Am I doing something wrong?
The files are correctly created in the Digital Ocean space dedicated to encoded videos.
It is also not possible to reprocess the file from WordPress as it says me the file already exists (in other words, but the essential meaning is this).
-
-
Hello Adamo,
thank you for reaching out to us!
Each try is a new job. If the first job failed it will stay as failed and there will be a second job created upon the second try. Also, the statuses do not change in realtime, so you have to refresh the page to see if a job has been finished/failed.
Does the second, successful, job show up in your FV Player Coconut dashboard or does it still show only the unsuccessful one?
A job that failed should not show up in the Coconut tab of media library picker either. Only the successfully encoded videos will.
Thanks,
Maria
Hello Maria,
first thank ou for your reply.I refreshed the page, but the status is still in “error”.
No new jobs were created and I cannot create a new one manually as I get an error message that says
> Target stream already exists, please try with different target name.
About this
> A job that failed should not show up in the Coconut tab of media library picker either. Only the successfully encoded videos will.
I’m not yet at this point: I’m first trying to convert the videos 😅
But, anyway, I think they correctly don’t show up there.
But the problem, for the moment, is that I have to encode again the video.
Hello Adamo,
Naming the files a bit differently should work, if that’s possible for you.
If you want to, you can check if files with the target stream name were created in your DigitalOcean Spaces bucket and possibly delete them, then try again.
Let us know, if it helped.
Thanks,
Maria
– I completely deleted all files in the space for the encoded videos on DigitalOcean
– I removed the videos from FV Player > Videos/PlaylistsIf I try to encode again the video, I continue to receive the same error.
How FV Player Coconut checks if the target file already exists? It should check on the DigitalOcean space, but there now there are no files: it is completely empty, so it is impossible it finds the target file there.
So maybe it checks in other places, a sort of “cache”, but where?
Ok, I found the problem!
The problem is the job in FV Player > Coconut jobs!
It seems FV Player checks the list of jobs to check if the video was already encoded or not.
At a first view, it seems the jobs cannot be deleted.
But if you hover over the ID of the job, then it appears the command to delete the job: once deleted, it is possible to encode the video again.
Hello Adamo,
we are glad to here you were able to resolve the issue and help others who might experience this in the future.
I’ll forward this thread to our development team, so that they are aware of this happening, and possibly make this less confusing or devise an easier workaround.
Thanks,
Maria
The easier thing that can be done, is to use checkboxes as in every other part of wordpress, so it is more intuitive that it is possible to act on jobs.
It was a mere fortuity I discovered I can delete jobs
Hello Adamo,
we will change that delete link to look like a standard WordPress post table row action – showing on hover in red color. That is the standard WordPress interface principle which we missed here.
Thanks,
Martin
