Workspace Errors

Here, you can find troubleshooting instructions for all errors that happen inside the Creator Studio workspaces.

Error Code: 13120

Error Message: There are validation errors in the email allow list. Please ensure all emails are formatted properly and there are no duplicates

1. Possible Cause: Duplicate Emails

We recommend checking & removing duplicate emails.

For small email lists (<20) you can ctrl + f or cmd + f and copy & paste each email into the search bar. For larger lists (>20), you can dump your emails into Google Sheets or Excel and remove duplicates.

2. Possible Cause: Invalid Email Format

We recommend looking for malformed email addresses:

Doesn’t have an @domain (e.g. @moveworks.ai )
Has an @domain that is different than what your org uses (e.g. @moveworks.com instead of @moveworks.ai )

For small email lists (<20)m you can ctrl + f or cmd + f and type the correct @domain into the search bar. For larger lists (>20), you can dump your emails in Google Sheets or MSFT Excel sheet and search the correct @domain.

Error Code: 10113

Error Message: Failed to make API request

This error message forwards the response of the original API Request.

We recommend setting this Endpoint up in Postman or a similar API testing tool before configuring in Creator Studio. Once you have this working, make sure to recreate your API Request in Creator Studio with all of the Query Params, Headers, & Request Body details that you had working in Postman.

Error Message: 10118

Possible Cause 1: Missing HTTPS

Check if the base URL in your connector starts with https://

Possible Cause 2: Invalid Port

It’s common that when using Azure or Power Automate, you will generate a webhook that looks similar to this:

prod-100.moveworks.azure.com:444

Instead, you need to remove the port # when making your connector:

prod-100.moveworks.azure.com

Error Code: 10111

Error Message: Failed to construct request. Please make sure that all variables denoted by {{}} have corresponding example values

Possible Cause 1: Missing Variable

In your error message, you may a detail that says “missing variable \”okta\” or some other variable. This means that variable was never defined:

In Paths Workspace, you need to create a new Question with the label “{{variable name}}” (e.g “okta”) in order to resolve.
In Queries Workspace, you can only use the {{query}} variable & user attributes . Creating additional variables is not allowed.

Possible Cause 2: Incorrect “{{}}” Syntax

Make sure all of your variables are wrapped in:

“{{}}” if they are strings
{{}} if they are numbers or booleans

Error Code: 10107

Error Message: Authorization failed

This error message is typically surfaced when the Connector tied to your API is using a 2-step Auth method and needs to hit a endpoint before making the primary request. This error message forwards the response of the original authentication (e.g. /token ) Request.

e.g. In OAuth 2.0 Client Credentials, we first make a request to a /token endpoint in order to get an Access Token. We then use that Access Token to make the primary request.

Error Code: 13107

Error Message: There are syntax errors in the rules provided in “Launch to the users matching the rule” step

1. Possible Cause: token recognition error at ‘=’

This means that you are using an incorrect operator. Check our Launch Rules reference for a list of supported operators

2. Possible Cause: extraneous input '==’

This means you are using an extra operator that doesn’t need to be included

e.g. user.role == “Engineering” == — In this case, the last set of == is “extraneous” and not needed.

Error Code: 13102

Error Message: Please return to “Triggering and parameters” step

1. Possible Cause: Make sure to provide the slots in all example queries

In order to resolve this issue, you need to add slot examples for all example utterances.

Incorrect

Correct

2. Possible Cause: Make sure to provide example value for slot for all utterances (for 1 slot Query) OR remove all example values (for 0 slot Query)

For Queries with 1 slot, you need to add Slots to each example user utterance in the triggering step.

For Queries with 0 slots, you need to remove all Slots in the triggering step.

Incorrect

Correct

3. Possible Cause: Make sure the slot value example provided is a part of user utterance example

You have a slot example value defined but it’s not a part of the user utterance that slot is attached to.

Incorrect

Correct

Issue: NLU trigger examples are not populating

Possible Cause: Poor plugin description

If you set up your Plugin basic info (title & short description) with confusing or gibberish values, it can cause recommended triggering utterances to fail.

To fix: ✅ Rephrase your description to be specific.

Incorrect

Correct