Reuse a job setup
Two ways to avoid rebuilding a job. Duplicate for a one-off variation. Template when you or your team will run this shape of job repeatedly.
Which one
Rule of thumb: duplicating is for you, now. A template is for your team, repeatedly.
Duplicate a job
From the jobs list, hover the row and click Duplicate, or open the job and use Duplicate there.
You land on the job setup page with everything carried over: input files, software, hardware, and post-processing. The name gains a (Duplicated) suffix.
Change what you need, then submit.
The duplicate is fully independent. The original's configuration, status, and results are untouched, so duplicating a colleague's shared job is a safe way to build on their work.
Duplicated jobs show their origin in the Lineage column, so a study stays traceable.
Save a template
A template captures the hardware, software selections, license variables, and general input files, so a new job starts from a known-good configuration instead of a blank form. It also carries any custom fields defined on the job, along with values you pre-filled, so a team can share a set of fields without an administrator setting them workspace-wide.
From a configured job, open the Save dropdown and choose Save as Template. Name it and add a short description.
To make a template from a job that already ran: duplicate it first, then save the duplicate as a template.
Before saving, make sure:
- Hardware is configured — coretype, cores, and walltime
- At least one software selection exists
The real value isn't saved keystrokes. It's that everyone running an FEA job runs it the same way, on the same hardware, with the same solver version. That makes results comparable across a team and across time.
Launch from a template
Templates are offered the moment you start a job. Click New Job and the drawer that opens lists them below the blank-job option, so the fastest path is usually to scan it before starting from scratch.
Each entry shows the coretype and core count, the software and version, the wall time, any tags, and who created it. Search by name with the box at the top, then click Create from Template.
Templates you own and templates shared with you both appear here.
Manage templates
A template shared with you can be launched but not modified. To adapt it, launch a job from it, adjust, and save your own template.
The archive control is labelled "jobs" rather than "templates", same button, it does apply to templates.
Share a template
Templates can be shared with colleagues and teams, the same way jobs are shared. Recipients can launch but not edit.
Admin restrictions
Workspace admins can:
- Restrict who can create templates.
- Require that jobs be created only from templates, blocking from-scratch creation entirely.
If you can't create a job from scratch, that second policy is why. It's typically used where runs must be standardized for compliance or cost control.
Related
- Create and submit a job — the flow a template replaces
- Find and manage your jobs — the Lineage column
- Share a job — sharing mechanics
- Workstation templates — the same feature for workstations
- Templates — a saved job or desktop configuration