All Collections
Automation
Workflows
Why did my Workflow fail at its Create Public Form step?
Why did my Workflow fail at its Create Public Form step?

Troubleshoot a Workflow failure occurring during your "Create Public Form" Workflow step.

Updated over a week ago

When you share a link using the Create a Public Form Workflow step you select Editable fields to determine which Form fields your recipient fills out. Errors in your editable field’s details will cause your Workflow to fail.

When troubleshooting this issue, common causes of failure include formatting or spelling errors, or a fields absence from the Workflow's associated Templates. As a result, your Workflow attempts to reference a field that doesn’t exist.

The procedure to resolve this issue is to first diagnose the issue by finding your problem field. Next, you’ll determine whether you need to resolve the problem in your Workflow step, or on your Template.

Locate your problem field

In the GoFormz web app, you’ll navigate to the Workflows tab and access the Jobs section.

  1. Locate and access the Workflow that is failing at the Create Public Form step.

    Screenshot displaying the Workflow Jobs section in the GoFormz web app with a Workflows name, failed step, and the status of “Failed” highlighted.


    You’ll navigate to the Workflow job details page.

  2. Your Workflow’s steps display here with the failed steps highlighted along with a description of the cause of failure.

    Screenshot displaying a failed “Create Public Form” step in the Workflow Job details page of the GoFormz web app.


    In this case, you’ll find “Field (your problem field’s name) does not exist” indicating the field you need to address. This list will include all of your problem fields.


    Make note of your problem field’s name - you’ll need it to fix this issue.

If you recognize an error with spelling, formatting, or syntax, you’ll resolve the error within the Create Public Form Workflow step.

But, if you recognize the field name as information you want your Public Form recipient to fill out, you’ll want to verify the field name on your Template.

Resolve an error in your Workflow step

After you’ve located and made note of your problem field, you’ll address the field in your Workflow. Use this method if you either recognize the error in your problem field name, or the problem field name was included in error.

Continuing from the Locate your problem field steps above, click View Workflow to open your Workflow in the Workflow Editor.

Screenshot displaying the Workflow Job details page in the GoFormz web app with an indication to click “View Workflow”.

You’ll navigate to the Workflow Editor.

  1. In your Workflow’s Create Public Form step, locate the Editable fields details.

    Screenshot displaying the Create Public Form step in the Workflow Recipe Builder with the Editable Fields details highlighted and displaying a problem field name.


    Here you’ll find your problem field.

  2. In Editable fields, select your problem field name.
    Enter the necessary edits, or delete the non-existent field.

  3. Click Save.

Verify that your changes resolved your issue by rerunning your Workflow.

Resolve the error by adding your problem field's name to your Template

Once you’ve located your problem field, you may recognize the field name as information you want your Public Form recipient to fill out.

To resolve this error, you’ll need to verify that the field’s name on your Template and the field name in your Workflow’s Editable fields are identical in spelling and formatting. You’ll also need to know which Template is referenced in your failing Workflow.

🗒️ Note: Verify the referenced Template for a Workflow when you access the Workflow’s trigger step. You’ll find the Template name listed under Select your Template.

On the GoFormz web app, navigate to the Templates tab where you’ll follow these steps:

  1. Locate the Template referenced in your failing Workflow.
    Open your Template in the Template Editor.

  2. Locate the field that contains your problem field name.

    Screenshot displaying the location of the Name field property in the Template Editor of the GoFormz web app with “Think” with a uppercase “T” entered as the field name.


    When you click each field, you’ll find its name in the Properties panel.

  3. Edit the field name on your Template.
    Your field name must match your problem field name exactly as it’s spelled and formatted in your Workflow recipe.

    Screenshot displaying the location of the Name field property in the Template Editor of the GoFormz web app with “think” with a lowercase “t” entered as the field name.


  4. Click Publish.

To verify that your issue is resolved, you’ll need to update your Workflow's related Forms to match your newly published Template version. With the Forms updated to the most recent Template version, rerun your Workflow.

What if my Workflow trigger uses multiple Templates?

If your Workflow trigger includes All Templates, then your Workflow may fail because your problem field doesn’t appear on every Template.

To resolve this issue, add a field to the necessary Templates and assign its name as your problem field’s name. In order to prevent confusion for your Form User, delete the new instance of your problem field from your Template, but leave it as an unmapped field.

Screenshot displaying the unmapped field modal in the Template Editor of the GoFormz web app.

As an unmapped field your Form Users will not be able to interact with the field. But, its existence will allow your Workflow to succeed.

Next, you’ll update your Workflow's related Forms to match your newly published Template version. With the Forms updated to the most recent Template version, rerun your Workflow.

If you’re still encountering this issue after you’ve adjusted your Workflow or Template as outlined above, please contact GoFormz Support.

Did this answer your question?