Copy a workflow
- Synopsis
- Full Details
In briefCopy Workflow creates a new, independent workflow from an existing one — its settings, frequencies and, by default, its jobs. The copy is made from the last committed version, is created in the General workspace, and is not deployed anywhere until you deploy it.
WhereDesign › Workflows, open the workflow, then Copy Workflow on the workflow editor's toolbar. The button is unavailable until the workflow has been saved, or when your role does not permit it; its tooltip says which.
When
- You need a second workflow structurally like one you already trust — another region, another institution.
- You want one job from this workflow in another one — use Copy to Another Workflow on the job instead.
- You want a starting point with the same build settings and frequencies but your own jobs (clear Copy jobs).
How
- Commit any changes you want carried across — a browser draft is not copied.
- Select Copy Workflow, and accept or change the suggested
<name> - Copy. - Leave Copy jobs and Navigate to this workflow after copy on, or clear them.
- Save, then review the copy's workspace, build settings and cross-workflow dependencies before deploying it. The task walkthrough is Add jobs to a workflow.
- Workflow names are 1–40 characters and reject
'|;%&<>()[]{},=!\". The dialog checks the name as you type. - Every copied job is a new job, and dependencies on jobs in the same workflow are repointed at the copy's own jobs.
- A name already in use is only reported when you save.
- Copy to Another Workflow copies one saved job into another workflow's unsaved changes and opens it in the Job Editor there; commit that workflow to keep it. See Copy one job to another workflow.
- Dependencies on jobs in other workflows are kept, so the copy waits on the same external predecessors as the source.
- Your role needs permission to create workflows in General, or the copy is refused.
- Copy auto/copy privileges has no effect yet.
Task walkthrough: Add jobs to a workflow. This page is the full reference for what a copy carries across.
Copy Workflow creates a new workflow from an existing one. It is the usual way to start a second workflow that is structurally similar to one you already trust — a statement run for a second region, or a nightly core export for a second institution — without rebuilding it.
The copy is a new workflow from the moment it is created. It is not linked to its source: editing either one afterwards has no effect on the other.
Making a copy
Copy Workflow is on the toolbar of the workflow editor. It is unavailable in two cases, and the tooltip tells you which one applies:
| The button is disabled because | What to do |
|---|---|
| The workflow has never been saved | Save it first. There is nothing to copy until it exists. |
| Your role does not permit it | The tooltip names the permission you are missing. See Roles and permissions. |
Two things about a copy are easy to get wrong:
- The copy is made from the last committed version, not from what is on your screen. Edits that are only in your browser's auto-saved draft are not carried across. Commit them first if you want them in the copy.
- The copy is always created in the General workspace, whatever workspace the source belongs to. Your role needs permission to create workflows in General, or the copy is refused. To put the copy somewhere else, change its Workspace in the copy's Workflow Settings panel and commit. See Workspaces.
The dialog asks for a name and offers three options.
A workflow can also be copied from global search. That dialog asks only for the name: the copy always carries the jobs, and is made the same way in every other respect.
Workflow name
The name defaults to the source name with - Copy appended. A long source name is truncated
so the result still fits the limit, rather than offering you a default the save would reject.
Workflow names follow their own, stricter rules, which are not the same as the rules for most other objects in Continuum — see Object naming:
| Rule | Value |
|---|---|
| Maximum length | 40 characters |
| Minimum length | 1 character |
| Rejected characters | ' | ; % & < > ( ) [ ] { } , = ! \ " |
Hyphens, slashes, spaces and accented letters are all accepted. The dialog checks the name as you type and applies the same rules the save applies, so a name the dialog accepts is one the save will accept.
Save stays unavailable while the name is empty or fails a rule. A name already in use is only detected when you save, and reports a name conflict.
Copy jobs
On by default. Every job in the source workflow is copied along with it.
Each copied job is a new job, not a second reference to the original. This matters more than it sounds: a job's identity is what other objects point at, so if a copy reused it, a notification group naming that job would fire for the original and the copy. Copied jobs are given fresh identities so that cannot happen.
Clear this option to copy the workflow's settings and structure only — build settings, frequencies, calendars — and add jobs yourself afterwards. The workspace is not carried across either way; see Making a copy.
Navigate to this workflow after copy
On by default. Opens the new workflow in the editor as soon as it is created. Clear it to stay on the source workflow; the copy is created either way and is available from the workflow list.
Copy auto/copy privileges
The control appears on the dialog and can be selected, but nothing is carried across by it — the copy is created exactly as though it were left clear. It is off by default, so an ordinary copy is unaffected. Set access on the copy through its workspace and roles instead; see Roles and permissions.
What happens to dependencies
Dependencies are the one part of a copy that needs thinking about, because a dependency names a predecessor and a copy changes which workflow that name resolves in.
| The dependency points at | In the copy |
|---|---|
| A job in the same workflow | Rewritten to point at the copy's own job. The copy is self-contained: its internal sequencing is preserved and does not reach back into the source workflow. |
| A job in a different workflow | Left as it is. That workflow is untouched by the copy, so the dependency keeps pointing at it — and the copy will wait on it exactly as the source does. |
A copy keeps every reference the original has, including those to workflows, thresholds and resources in workspaces your role cannot view: a reference carried over unchanged is not checked against your access. You need View on the workflow you copy. A reference you add or change in the copy is checked as on any save — see A dependency on a workflow you cannot view. The same holds for container jobs and agents: a copy keeps the sub-workflow each container job runs, even one no longer marked Sub-Workflow, and the agent each job names, without checking them again.
The second row is the one to check after copying. If you are copying a workflow in order to run an independent second stream, a cross-workflow dependency means both streams still wait on the same external predecessor, which may or may not be what you want.
After the copy
The copy is created as a new, undeployed workflow. Nothing about the source's deployment carries across — deploy the copy deliberately when it is ready. See Versions and deployments.
Review at least these before deploying:
- Workspace. The copy is in General. Move it if it belongs elsewhere.
- Build settings. The copy inherits Auto Build, Days in Advance, Days to Build, Overwrite on Build, Build on Hold and the rest. Two workflows building the same dates is usually intended; two workflows both configured to build unattended may not be. See Scheduling and the run.
- Cross-workflow dependencies, per the table above.
- Properties and tags. Property references are carried by name, so the copy resolves them the same way the source does — including any that are environment-specific.
Copy one job to another workflow
To reuse a single job rather than a whole workflow, open the job's menu on the canvas — the menu on its card, or its context menu — and choose Copy to Another Workflow. It is offered for one job at a time, on a workflow that has been saved, and not on a canvas you can only view.
The copy is the job as saved in the current version, not what is on your screen. A job you have added or changed since the last commit is offered greyed out, with the tooltip Save this job to a version before you copy it to another workflow.
The Copy Job to Workflow dialog asks for two things:
| Field | Notes |
|---|---|
| Target Workflow | Required. Any workflow but the one you are in. Your role needs permission to edit workflows in the target's workspace; if it does not, the dialog says so and Copy stays unavailable. |
| Job Name | Required. Starts as the job's own name. It must be unique in the target workflow, ignoring case, and at most 255 characters — the same rules as any job name. It is checked against the target as it stands, including any unsaved changes you have in it. |
What the copy carries:
- It is a new job, with its own identity, like a job in a copied workflow.
- Dependencies on jobs in the source workflow keep pointing at the source workflow's jobs. The
dialog warns how many, for example 1 dependency will still point to a job in
<source>. Remove or repoint them in the target if the copy should not wait on the source. - Frequencies are matched by name in the target. When the target workflow has frequencies, a
frequency of the job that the target does not have is dropped, with any event scoped to it. The
dialog names them first: These frequencies are not in
<target>and will not be copied: …
The copy lands in the target's unsaved changes, not in a new version. Selecting Copy adds the job to the target workflow's draft in your browser, opens the target workflow, and opens the copy in the Job Editor. Review it, then commit the target workflow to keep it. Any other unsaved changes you already had in the target are kept alongside it.
If the workflow you are leaving has unsaved changes, you are asked whether to discard them first.
Cancelling keeps you where you are, and the copy stays in the target's unsaved changes: The copy of
<job> is in the unsaved changes of <workflow>. It is saved when you save that workflow.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Copy Workflow is greyed out | The workflow has never been saved, or your role does not allow it | Read the tooltip: it distinguishes the two. Save first, or ask for the permission it names. |
| Save stays unavailable in the dialog | The name is empty, longer than 40 characters, or contains a rejected character | The field shows which rule failed. Shorten the name or remove the character. |
| Saving reports a name conflict | A workflow already uses that name | Choose another. Names are matched without regard to case, so changing only capitalisation does not resolve it. |
| The copy is in the General workspace, not the source's | A copy is always created in General | Change the copy's Workspace in Workflow Settings and commit. |
| The copy is missing changes you had just made | The copy is made from the last committed version; your browser draft is not included | Commit the source first, then copy it again. |
| The copy is refused for permission although Copy Workflow was available | Your role can create workflows, but not in the General workspace | Ask for permission to create workflows in General. |
| The copy is refused with This workflow can't be copied: it references something that doesn't exist or that you don't have access to, followed by the first problem | The original references a workflow, threshold, resource or other object that has since been deleted or cannot be found | Fix or remove that reference on the original, commit, and copy again. The message names the job and the reference, such as job 2 — Workflow 'X' not found. |
| The copy waits on a job that has nothing to do with it | The source had a cross-workflow dependency, which is deliberately preserved | Remove or repoint that dependency on the copy. |
| Selecting Copy auto/copy privileges carried no access across | That control has no effect yet | Expected. Grant access on the copy through its workspace and roles. |
| Copy to Another Workflow is greyed out on a job | The job has been added or changed since the last commit | Commit the workflow, then copy the job. |
| The copy could not be saved in this browser. Free some browser storage, then try again. | The browser refused to store the target's draft | Free browser storage and select Copy again. Nothing was copied. |
| The workflow could not be loaded. Choose it again or try later. | The target workflow could not be read | Choose the target again, or try later. |
| The copied job is not in this workflow, so the Job Editor did not open. | The target workflow opened without the copy in it | Open the source workflow and copy the job again. |