[
http://opencast.jira.com/browse/MH-7144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=25225#comment-25225
]
Adam Hochman commented on MH-7144:
----------------------------------
I suggest WARNING instead. WARNING: Recording may have failed to start or
ingest.
As we discussed earlier, recordings stuck in upcoming need to be handled in
this manner.
Benjamin I did notice however that recordings go into this state briefly even
if they successfully start. It appears that your logic is a bit aggressive in
determining this warning state. Most likely your average user isn't following
progress on upcoming, but institutions that first set up Matterhorn will
definitely be confused that this happens even when the capture starts capture
correctly. There have been several times where I thought the capture agent was
down. Is it possible to delay this logic to allow for the capture agent to
register its progress?
> Admin UI does not show failed workflows in failed section
> ---------------------------------------------------------
>
> Key: MH-7144
> URL: http://opencast.jira.com/browse/MH-7144
> Project: Matterhorn Project
> Issue Type: Bug
> Components: Administrative Tools, Architecture & Services
> Affects Versions: 1.1
> Reporter: Ruediger Rolf
> Assignee: Benjamin Wulff
> Priority: Release Blocker
> Fix For: 1.1
>
> Attachments: failed-missing.PNG
>
>
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________