Skip to main content

Troubleshooting - OM Task Workability & Ce6 Accessibility

Tristan Weber
Updated

 

 

Basics

  • This article is primarily meant as a reference guide for editors and linguists but it can be used by anyone.
  • The goal of this article is to provide some quick steps to get unstuck -- this is not meant to be a comprehensive troubleshooting guide, nor are you expected to become a troubleshooting expert...!
  • Golden rule: if you cannot solve the Task workability or Ce inaccessibility issue(s) within 15 minutes, send a support ticket. Ensure you always CC the PM. Include the troubleshooting steps you already attempted in the ticket description.

 

 

What Problem Are You Facing?

Click one of the links below to jump to the relevant instructions:

Click here for a video explanation of key elements within OM Jobs and Tasks.

 

 

Ce6 Button is Greyed Out

If your OM Task is WORKABLE but you CANNOT access Ce6...

 

1. Within your Task, scroll down to “Additional Details”, expand if needed, then click the robot icon:

 

2. Click “Executions”, then scroll down and look for any FAILED executions (RED):

 

3. If you see any failed executions OR if you don’t see either “Ce - Create Ce Scripting Project” or “Ce - Create Ce Project” listed, go to the top of the Task to find the “Priority” field:

 

4. Change the Priority to “5 - On Hold”. Wait until you get the refresh pop up, click it, then change the Priority back.

 

5. Go back to the Task’s executions (bottom of Task > robot icon > executions) -- you should see new executions that will start as “Pending” (orange) and move to “Success” (Green).

  • If any new executions FAIL or do not trigger within two minutes, send a support ticket. In the description, include a screenshot of the failed execution and indicate that you attempted to “toggle task priority” but the executions are still failing or have not triggered.
  • If the executions SUCCEED, wait two minutes. If the Ce button is still greyed out, send a support ticket. In the description, include that you attempted to “toggle task priority” and the executions have succeeded, but Ce is still inaccessible.

 

 

OM Task is Not Workable

First, let's categorize the workability impediment...

 

1. Scroll to the top of the task, and find the “Workability” field:

 

2. Hover over the red exclamation mark. What do you see? Click one of the links below for applicable troubleshooting instructions:

 

 

Workability Impeded By

If NOTHING is listed under “Workability Impeded By”, there is a system issue – BUT you may be able to fix it...

 

1. Within your Task, scroll down to the "Additional Details” section and hit the expander arrow if needed. Click the leftmost (picture) icon, labeled “Assets”, and scroll down to the “Input Requirements” section.

 

2. Beneath any Asset Shell, click the blue gear icon, then click “Done”:

  • This will attempt to refresh the Task workability.
  • If, after two minutes, the task remains “Not Workable”, there is one other thing to check...

3. Find the Asset Shell labeled “Proxy” under Input Requirements – if it is not listed as either “Available” or “Checked In”, the proxy either hasn’t arrived or is still ingesting:

  • In this case, flag to coordination and ask them to verify if the proxy has arrived.

4. However, if the proxy IS listed as either “Available” or “Checked In”, send a support ticket. In the description, include:

  • There is nothing listed under “Workability Impeded By”
  • The proxy appears to have successfully ingested
  • You attempted to refresh the Task workability

 

 

Workability Impeded By: Priority

If, when hovering over “Not Workable”, Workability Impeded By lists “Priority”: 

The system is saying that our Task workability is impeded by EITHER Task Priority or the Job Production Status...

 

1. Scroll up to the top of the Task and find the Priority field:

 

2. If Task Priority is either “5 - On Hold” or “6 - Cancelled”, someone manually put the task into this state.

  • In this case, flag to coordination to confirm if the task should be in this state.

3. If the Task Priority is anything else, go to the OM Job by clicking the hyperlinked Job Name in the top left of the page, then scroll to the very top to find the Job Production Status:

 

4. If the Job Production Status is either “5 - On Hold” or “6 - Cancelled”, this is impeding Task workability.

  • In this case, flag to coordination to confirm if the job should be in this state.

 

 

Workability Impeded By: InputRequirement

If, when hovering over “Not Workable”, Workability Impeded By lists “InputRequirement”...

1. Within your OM Task, scroll down to the "Additional Details” section and hit the expander arrow if needed. Click the leftmost (picture) icon, labeled “Assets”, and scroll down to the “Input Requirements” section.

 

2. First, check that all the Reference Materials are correctly listed as ‘Optional’ under their respective Asset Shells:

  • Note: by default, Reference Materials are published as “Optional”. However, if after publishing, a user manually adds a Shell for an unaccounted for asset, that Asset Shell defaults to “Required for Start”

3. If a Reference Material says “Required for Start”, click Actions to determine if the asset is accessible...

  • If “Show MAM Attributes” doesn’t exist an option, there is no asset available.
  • If the asset is not available, and we’re positive this is meant to be a Reference Material, flip to “Optional”.
  • If you’re unsure, or if you were given special instructions indicating that this unavailable asset is a requirement, double-check with coordination.

4. If all Reference Materials are correctly labeled "Optional", we should now check if all predecessor Tasks are complete. The colors on the lefthand side of the bars tell us their status:

  • RED = Pending 
  • BLUE = In Progress 
  • GREEN = Complete

5. If you have ANY Tasks in input requirements that are marked “Required for Start” that are either RED or BLUE, this will impede task workability, unless those Tasks are skipped.

  • To check if a Task is skipped, expand it, and look in the top left to see if "Skip this Task" is checked:
  • If there are un-skipped required Tasks, flag to coordination. Indicate which required Task(s) are incomplete.

6. If all required Tasks are complete (GREEN), look at each Asset Shell. Look for a red dot over the gear icon in the top right:

  • If none of the Asset Shells have a red dot, send a support ticket. In the description, include that “Workability Impeded By” is listing “InputRequirement”, but you can’t see any incomplete required tasks or required assets with missing tags.

7. For any Asset Shells with red dots, look at the status field in the bottom left. If there is an “X” on the right side of the field instead of a robot icon, this means that a user has manually flipped this status...

  • In this case, click the “X” and see what status it reverts to.
  • If it changes to “Awaiting”, the asset has not been successfully ingested into this Asset Shell. In this case, flag to coordination, indicating which required Asset Shell is not yet fulfilled.

8. If the Asset Shell's status field has a robot icon, click the gear in the top right to see what the delay is...

  • Note: there are three requirement categories for an Asset Shell. The specific requirements for each asset are determined by the OM Job Template.
    • "Asset Status": visible in the bottom left of the Asset Shell -- this category is unique in that it may list multiple Statuses (e.g., "AVAILABLE" and "CHECKED_IN"), but Task workability only ever requires ONE of the listed Statuses to be true – there is never a scenario where an asset is “CHECKED_IN” but needs to be “AVAILABLE” or vice versa.
    • "QC Types": all of the listed QC Types must be applied (BLUE) for the Task to be workable -- QC Types should never be manually applied. They are either applied by clicking a button (located elsewhere) or via a system automation.
    • "Tags": all of the listed Tags must be applied (BLUE) for the Task to be workable -- Tags should never be manually applied. They are either applied by clicking a button (located elsewhere) or via a system automation.
  • BLUE requirements are true/applied. WHITE requirements with RED DOTS are impeding workability:

  • In the above example, the Asset Status "AVAILABLE" and the QC Type "Production QC - Linear" are true and applied, respectively. However, the "Approved For Language Jobs" Tag has not been applied and is thus holding up Task workability.

9. What do you see? Click one of the links below for applicable troubleshooting instructions:

 

Asset Status Required for Task Workability

If NONE of the Asset Statuses Required for Task Workability are true (BLUE)...

Note: Task workability only ever requires ONE of the listed Asset Statuses to be true (BLUE) -- there is never a scenario where an asset is "AWAITING" but must be "CHECKED_IN" or vice versa.

1. In this case, the Asset Shell has not been successfully fulfilled. Depending on the asset, this can mean it hasn't been received, hasn't been ingested, hasn't been generated, or there was a setup issue.

2. Regardless, flag to coordination and include the specific asset shell that hasn't been fulfilled.

 

QC Types Requiring Pass for Task Workability

If ANY of the QC Types Requiring Pass for Task Workability are WHITE with a RED DOT...

 

1. In this case, a specific QC Type needs to be applied to the asset before the Task will become workable.

  • These QC Types are either applied after a user clicks a button (located elsewhere) or applied automatically by the system when certain criteria is met.

2. Regardless, send a support ticket. Include a screenshot of the missing QC Type. Ensure you CC the PM.

 

Tags Required for Task Workability

We must first determine if this Tag is an AM proxy generation / metadata sidecar...

 

1. If the Tag is any of the following, Task workability is being impeded by an AM proxy generation / metadata sidecar generation:

  • "Video Proxy Creation", "Audio Proxy Creation", "Audio Waveform Creation", "Shot Change Creation", "Shot Change Json Creation"
  • In this case, send a support ticket to GTS with the PM on CC. In the description, include a screenshot of the missing Tag, and ask them to double-check if the generation(s) have failed or require re-running.

2. If the Tag is anything else, it could either require a user to press a button or its meant to be applied automatically by the system once certain criteria is met.

  • Regardless, send a support ticket. Ensure you CC the PM, as some of these tags require them to press a button. Include a screenshot of the missing tag.

 

 

Workability Impeded By: Remediation

If, when hovering over “Not Workable”, Workability Impeded By lists “Remediation"...

 

1. This means a user has manually put the task into remediation via the "Remediation" dropdown field.

 

2. The user may have left a note explaining why it's in remediation -- click the speech bubble beside the "Remediation" dropdown field to check.

 

3. Flag to coordination, providing the comment(s) if applicable, and ask them to verify if the task is supposed to be in remediation.

 

 

Unable to Submit in Ce6

If you are unable to submit your file in Ce6...

 

1. Send a support ticket. Include:

  • Screenshot of the error (if applicable) that you see in Ce6
  • Link to the Task or Job (not just the Ce6 project)
  • In the description, specify which track you are attempting to submit (for ICS)

 

 

Video Explanation

The video linked below explains some basic information about how to read OM and investigate task workability:

https://support.pixelogicmedia.com/hc/en-us/articles/29220054338332-Task-Workability-Test-Article

Comments

0 comments

Please sign in to leave a comment.