Skip to main content

Troubleshooting Task Types

You can view the status of your Task Types in the Task Management screen. If there are any problems with your Tasks an error will appear in the status column next to your Task Type.

To find the overview of all Task Types available in your Studio package, go to your Studio package and select Task Management.

Overview of Task types screen

The Status column gives you an insight into the condition of your Task Types. If there are any issues with your Task Types, an error will be displayed in that column. Status is displayed only when there are any issues with Task Types.

We divided error types based on their importance:

Warnings in Task Types

Minor configuration issues are problems that don’t prevent Tasks from functioning but might affect their overall performance. Common minor issues are:

  • unpublished changes

  • missing Action Flow

  • missing assignee

  • missing group or user

The best way to resolve most minor issues is to edit a Task Type and add any missing values. See Editing Tasks Types. In case of any unpublished changes that might prevent Tasks from functioning properly, publish your Studio package for the changes to take effect. See Versioning and deploying.

Errors in Task Types

Major issues prevent Task Types from functioning completely. You must resolve all major issues to continue using Task Types. There can be many causes for these issues. Here are common ones with suggestions on how to solve them.

  • Failing activation

    During the first publication of a Task Type, an augmentation table was not created, or the Task Type didn't subscribe to the Trigger.

    Solution: Try publishing the package that contains the Task Type again using the retry button in the error information. If you still see the error, check if an augmentation table can be created for the Data Model table used in the Task Type. Finally, verify if the trigger used in this Task Type works correctly by going to Studio and selecting your package > your Knowledge Model >Triggers. For the most common errors with triggers and ways to solve them, see Triggers troubleshooting.

  • Missing Trigger

    The Trigger used in the Task Type does not exist.

    Solution: Create a new Trigger and add it to the Task Type. See Creating Triggers using Data Model. Make sure you create the new Trigger in the same Knowledge Model as the previous Trigger.

  • Missing Data Model table

    The Data Model or a Data Model table linked to the Task Type no longer exists, typically, due to user configuration issues.

    Solution:

    1. In Studio, go to your package > your Knowledge Model > Triggers.

    2. Edit the trigger associated with the Task Type.

    3. Specify a new Data Model table.