Skip to main content

Troubleshooting

You may encounter errors during the following steps of the tagger lifecycle:

  1. Validating sections of a tagger definition
  2. Enabling a tagger for normfill
  3. Reviewing invocation runtime results

This section provides guidance on how to resolve the most commonly encountered user errors. This list is not exhaustive, so contact us if you encounter an error you feel you have no way to resolve on your own.

Validation errors​

Validation errors occur when you attempt to move on to the next step of the tagger creation or editing process, but the current section contains errors. The most common reasons for these errors include the following:

  • Invalid characters or input type for a given form field
  • Import expressions that are not valid Python code or contain imports of modules that are not supported
  • Missing schema for the selected variable channel

To resolve a majority of validation errors, review the error messages shown and correct the issues.

A missing schema indicates that our platform has not yet registered a schema for the selected channel. Schemas for new channels are registered by our platform shortly after 12:00 AM UTC every 24 hours. You must therefore wait until the day after a robolog with the channel you want to tag is ingested before you can validate and invoke a tagger that uses that channel. Please contact us if you need to expedite this process.

Enable errors​

An attempt to enable a tagger with no successfully tested versions will result in an error. You must test at least one of the tagger versions—typically the latest published version—before enabling the tagger to run on newly ingested robologs.

Invocation errors​

Invocation errors occur during tagger invocation runtime. The most common reasons for these errors include the following:

  • The robolog being tagged is missing a channel referenced in the tagger definition's variables section.
  • A metadata field referenced in the tagger's output section does not exist because it was deleted or deactivated after the tagger version was published.
  • Evaluated import or calculate expressions result in a Python exception

To resolve these errors, review the error messages shown and correct the issues. If you are unable to resolve the issue, contact us for assistance.