Re-Runs v. Re-Opens

Basics

• This is a reference guide for Client Ops, English, and Territory.
• The goal is to demystify three buttons, located on Scripting and Subtitling Jobs:

• Re-Runs (and the associated button) are used when we receive a new proxy and need to revise a completed asset in Ce6.
• Re-Opens (and the associated buttons) are used for ANY OTHER time we need to revise a completed asset in Ce6 (e.g., to update for a internal flag).

What do you need to do?

Quickly Reference...

• How re-runs and re-opens work for scripting v. subtitling jobs
• How to choose between a manual re-run and a button

We received a new proxy AND...

• We need to revise a script
• We need to revise the initial subtitle
• We need to revise a downstream subtitle

We have NOT received a new proxy, BUT...

• We need to revise an English script
• We need to revise an ICS script
• We need to revise an English OR ICS subtitle

Scripting v. Subtitling | Quick Reference

*If we must revise a script at first proxy version, we must also publish a new Job to create a change list.

• Dev Idea: Can completion of the initial subtitle Job trigger the re-run for downstream Jobs?
  • I.e. can we make it so the button is only pressed once?

Manual Re-Runs v. Buttons | Quick Reference

• Golden Rule: if there's a button, use the button. Do not use manual re-runs unless it's the only option.
• Manual re-runs, when supported by the OM Job Template, are a way to force an individual task back to a "Pending" state. This Manual "Re-Run" actually functions closer to a Re-Open (maddening!).
• Manual re-runs are accomplished by opening the task and clicking the circular arrow in the top right:

• Manual re-runs should NEVER be used on tasks that can open Ce6 (e.g., script creation, subtitle QC).
  • While the Templates are meant to disallow this option, some older published jobs may still have this functionality. Initiating a manual re-run on these tasks can cause workability issues downstream.

Client Ops: Revise Script for New Proxy

In this case, the PM will always need to publish a new scripting Job.

In PMP:

• Group: Match to the new proxy version. This field cannot be blank.
• Additional Fields: Previous Source Version must match the previous proxy version EXACTLY.

Client Ops: Revise Initial Subtitle for New Proxy (Re-Run)

Context: 

• We received a new proxy version from client, requiring us to revise our existing subtitles.
• You are a PM, and you want subtitles revisions to begin.

1. Go to the initial subtitle Job (the job of the first asset that we will revise to match the new proxy version)

2. Open the final Task within the Job -- it will include "Project Management" in the Task name:

•  In the above example, our initial subtitle Job is the Temp-SDH

3. Scroll down to Additional Fields, click the "Re-run for New Proxy Version" button:

4. Only click the button ONCE. Wait 5 minutes.

• Below the button, you should see text reading "In progress" followed by "Automation succeeded"
• Note: clicking the button puts the requested action into a queue -- if you press the button more than once within 5 minutes, you're re-requesting the action, meaning your request will go to the bottom of the queue.

5. Once you see "Automation succeeded", refresh the page (ctrl+r).

• Note: to check that the successful re-run is reflecting in the job, you can double-check the run number on the ingest task -- it will go up by one number (e.g., "R1" to "R2"):

• If the "Automation succeeded" status does not appear within 5 minutes, click it again. Wait another 5 minutes. If it still does not appear, send a support ticket. In the description, explain whether the button status is stuck "In progress" or if no status appeared.
• If you instead receive an "Automation failed" status, do not click the button again. This is an OM Job Template issue. Send a support ticket with a link to the job and a screenshot of the failure status:

6. The CQC1 Task should switch back to "Workable" and "Pending" -- this is where we will revise the subtitle.

• If the Task does not switch to Workable/Pending, please consult the Task Workability section of the Troubleshooting Article for your department: (Client Ops | English | Territory)

Subtitling Dept: Revise Downstream Subtitle for New Proxy (Re-Run)

Context:

• We received a new proxy version from client, requiring us to revise our existing subtitles.
• PM has already re-run the initial subtitle Job. That revision is complete. Now, we want to begin conforming.

1. Go to the downstream subtitle Job.

2. Open the CQC1 Task within the Job -- identify this by the Task Tag:

3. Scroll down to Additional Fields, click the "Re-run Job for New Proxy" button:

• Note: the text on the button may vary slightly (e.g., "Rerun Job for New Proxy" v. "Re-run Proxy for New Version") -- as long as the button contains "Rerun/Re-run" and "New Proxy", it will do the same thing.

4. Only click the button ONCE. Wait 5 minutes.

• Below the button, you should see text reading "In progress" followed by "Automation succeeded"
• Note: clicking the button puts the requested action into a queue -- if you press the button more than once within 5 minutes, you're re-requesting the action, meaning your request will go to the bottom of the queue.

5. Once you see "Automation succeeded", refresh the page (ctrl+r).

• Note: to check that the successful re-run is reflecting in the job, you can double-check the run number on the ingest task -- it will go up one number (e.g., "R1" to "R2"):

• If the "Automation succeeded" status does not appear within 5 minutes, click it again. Wait another 5 minutes. If it still does not appear, send a support ticket. In the description, explain whether the button status is stuck "In progress" or if no status appeared.
• If you instead receive an "Automation failed" status, do not click the button again. This is an OM Job Template issue. Send a support ticket with a link to the job and a screenshot of the failure status:

6. The CQC1 Task should switch back to "Workable" and "Pending" -- this is where we will revise.

• If the Task does not switch to Workable/Pending, please consult the Task Workability section of the Troubleshooting Article for your department: (Client Ops | English | Territory)

7. Within the CQC1 Task, scroll down to Additional Fields > Input Requirements. Ensure your "Proxy" and "Source" Asset Shells do not have an orange alert icon in the top-right. If they do, click on the asset version dropdown and select the option that includes "Latest":

English Scripting: Re-Open to Update

Context:

• If we are at FIRST proxy version, we CANNOT use the re-open button if we want a change list. To make updates to a script at first proxy version, the PM will need to publish a new Job.
• For the process below, we must be at second proxy version or later -- OR, we do not need a change list.
  • English coordination and Client Ops will need to communicate to determine if a change list is required and if this file has already been delivered to client.
• You are an editor working on an English Job.

1. Go to the English Scripting Job that, without being prompted by a new proxy, requires an update.

2. Open the CQC1 Task within the Job -- identify this by the Task Tag:

3. Within the Task, scroll down to Additional Details. Click the "Reopen Task for DL Update" button:

4. Only click the button ONCE. Wait 5 minutes.

• Below the button, you should see text reading "In progress" followed by "Automation succeeded"
• Note: clicking the button puts the requested action into a queue -- if you press the button more than once within 5 minutes, you're re-requesting the action, meaning your request will go to the bottom of the queue.

5. The CQC1 Task should change back to "Workable" and "Pending".

• Note: upon successful execution of the re-open button, the subtitle Asset Shell will version up. It will not flip from "Awaiting" to "Available" until the file is submitted in Ce.
• Note: this should NOT impede downstream Translation with Template Jobs.
• If the Task does not switch to Workable/Pending, please consult the Task Workability section of the Troubleshooting Article for your department: (Client Ops | English | Territory)

6. Open Ce, make updates, and make new exports.

• Note: remember to label the exports. The proxy version is the same, but include "update X" in both the file name and the asset version name in OM.

7. In your PP doc, you will need to manually highlight the updates, that way, the changelog should have the previous proxy version to current proxy version changes in one color, and these new updates in another.

• Note: Client Ops can download this document from the final ("Project Management" Task within the Job).

ICS Scripting: Re-Open to Update

Context:

• If we are at FIRST proxy version, we CANNOT use the Re-Open button if we want a change list. To make updates to a script at first proxy version, the PM will need to publish a new Job.
• For the process below, we must be at second proxy version or later -- OR, we do not need a change list.
  • ICS coordination and Client Ops will need to communicate to determine if a change list is required and if this file has already been delivered to client.
• You are an editor working on an ICS Job.

1. Go to the ICS Scripting Job that, without having received a new proxy, requires an update.

2. Open Task 17 within the Job:

3. Within the Task, scroll down to Additional Details. Click the "Reopen Task for Update" button:

4. Only click the button ONCE. Wait 5 minutes.

• Below the button, you should see text reading "In progress" followed by "Automation succeeded"
• Note: clicking the button puts the requested action into a queue -- if you press the button more than once within 5 minutes, you're re-requesting the action, meaning your request will go to the bottom of the queue.

5. Task 17 should change back to "Workable" and "Pending".

• Note: upon successful execution of the re-open button, the subtitle Asset Shell will version up. It will not flip from "Awaiting" to "Available" until the file is submitted in Ce.
• If the Task does not switch to Workable/Pending, please consult the Task Workability section of the Troubleshooting Article for your department: (Client Ops | English | Territory)

6. Within Task 17, open Ce, make updates, and make new exports.

• Note: remember to label the exports. The proxy version is the same, but include "update X" in both the file name and the asset version name in OM.

7. In your PP doc, you will need to manually highlight the updates, that way, the changelog should have the previous proxy version to current proxy version changes in one color, and these new updates in another.

• Note: Client Ops can download this document from the final ("Project Management" Task within the Job).

English/ICS Subtitling: Re-Open to Update

Context:

• Use the "Reopen Completed Job to CQC1 for Update" button whenever you need to revise a subtitle WITHOUT having received a new proxy.
• You are a subtitling editor working on an English OR ICS Job. This process is the same at any proxy version.

1. Go to the English subtitle Job where you intend to make the update.

2. Open the CQC1 Task within the Job -- identify this by the Task Tag:

3. Within the Task, scroll down to Additional Details. Click "Reopen Completed Job to CQC1 for Update" button:

4. Only click the button ONCE. Wait 5 minutes.

• Below the button, you should see text reading "In progress" followed by "Automation succeeded"
• Note: clicking the button puts the requested action into a queue -- if you press the button more than once within 5 minutes, you're re-requesting the action, meaning your request will go to the bottom of the queue.

5. The CQC1 Task should change back to "Workable" and "Pending".

• Note: upon successful execution of the re-open button, the subtitle Asset Shell will version up. It will not flip from "Awaiting" to "Available" until the file is submitted in Ce.
• If the Task does not switch to Workable/Pending, please consult the Task Workability section of the Troubleshooting Article for your department: (Client Ops | English | Territory)

Issue Brought up on Daily Ops Call – Subtitle (Temp-Full)

• Re-Run Job For New Proxy
• Task 4 (creation) was auto-skipped, correctly
• Task 5 (CQC) has reopened – English
  • Somehow, though, the task has become not workable
  • Now, English is supposedly working out of Task 4 (creation)
• This would require WFA permissions to reopen creation?
  • Was it GTS?
  • Note: English is only meant to do the Creation task one time
• It looks like an ICS linguist (freelancer) was assigned to Task 4 – they need a place to do their QC
  • Can’t QC out of a sidecar job currently – but they’re supposed to be able to work out of this
    • This may be a template enhancement request
  • Need to document whatever the correct procedure is here