When building or editing a Dashpivot template, a range of validation checks run before the template is saved. These checks cover your template's name, ID, type, thumbnail settings, and the integrity of the template itself.
This article explains each error message you might see and how to resolve it.
"Template name is required." / "Template Name cannot be blank or have slashes." / "Give your untitled template a name before saving."
Why this happens
These three messages all relate to the template name field. The first appears when the name is completely empty, the second when it contains a forward slash (/), and the third is a warning while the template is still named "Untitled." Template names cannot be blank or contain slashes — forward slashes break path parsing in the system.
How to fix it
Click the template name at the top of the editor.
Enter a name that is not blank and does not contain slashes (
/).Save the template again.
"Template ID has been used."
Why this happens
The Template ID you entered is already in use by another template in your account. Template IDs must be unique and cannot be reused, even if the original template was archived or deleted.
How to fix it
Go to Template Settings and find the Template ID field.
Enter a different, unique ID.
Save the template again.
"Template type is required."
Why this happens
The template type (e.g. Standard, Workflow, Actions) has not been set. This is usually configured when a template is first created, but may be missing if the template was imported via JSON.
How to fix it
Open Template Settings.
Select the appropriate template type.
Save the template again.
"We couldn't save your template. Please try again, or contact support."
Why this happens
This error indicates a server-side save failure. One common hidden cause: if you edited the template's raw JSON and removed or renamed a field that was previously selected under Template Settings → Display on Form Thumbnail, the thumbnail setting becomes invalid and will silently block the save.
How to fix it
Refresh the page and try saving again.
If the error persists, go to Template Settings → Display on Form Thumbnail and verify that all selected fields still exist in the template. Remove any references to fields that no longer exist, then try saving again.
If neither step works, contact support.
"You need to save your changes before you can clone this template."
Why this happens
Cloning creates a copy of the last saved version of the template. To ensure the clone reflects your latest edits, you must save first.
How to fix it
Save the template.
Once saved, proceed with cloning.
"Unable to deploy template" / "Unable to deploy templates." / "Unable to undeploy templates."
Why this happens
This is a server-side error that typically occurs during a temporary service disruption or network failure.
How to fix it
Wait a moment and try again.
If the issue persists, contact support.
"Storm could not complete this edit. Please try again." / "Storm could not continue this edit. Please try again."
Why this happens
These errors appear when you are using Storm to make edits directly inside the template editor. The first message means Storm failed to complete the edit request. The second means Storm failed to resume an edit that was already in progress. Both are caused by a temporary AI service disruption.
How to fix it
Wait a moment and try the request again.
If the error persists, save any manual changes you have made and refresh the page before retrying.
If Storm continues to be unavailable, contact support.
If the issue continues
If you have followed the steps above and the error is still appearing:
Try refreshing the page and repeating the action.
Check for any active service disruptions on the [Sitemate Status Page].
Contact support with the name of the template you were editing and a description of the steps you took — this helps our team resolve the issue faster.