Skip to content

Why does Put Live fail?

You try to put your configuration changes live, but Atfinity will not let you. Before your changes take effect, Atfinity checks the whole configuration and reports two kinds of message.

Warnings do not block Put Live

A warning points at something that is probably not what you intended, for example a rule you created but never added to a process. Warnings do not prevent you from putting live. Review each one, and either fix it or put live anyway if it is expected.

Errors block Put Live

A fatal error means the configuration is inconsistent and cannot be applied. As long as at least one error remains, the 'Put Live' action stays disabled. Each error names the part of the configuration that is broken, so work through the list and resolve them one by one.

Common causes of errors are:

  • A rule or condition with a syntax mistake in its RuLa expression.
  • A reference to an information, ontology, or document that has since been deleted or renamed.
  • A document that is referenced by a process but no longer exists.
  • A type mismatch, for example an expression that tries to combine a number and a string.

After fixing the errors

Once every error is resolved, put live and test the change in a new case to confirm it behaves as intended. See Put Live for the full walkthrough.

Errors that only show up in a running case

Put Live catches configuration errors. Some problems, such as an expression that fails only for a particular set of answers, appear once a case is running instead. Those surface in Case Errors.