Develop > Wizards > Troubleshooting > Wizard stops with "Could not continue" errors

Wizard stops with "Could not continue" errors

The wizard stops executing for a variety of reasons, including possible configuration errors. Some of the errors you may encounter are as follows:
 

Error Cause/Fix

Cannot create record of type "test."

Cause: The record type entered does not exist as a record in the dbdict table.

Fix: Enter a valid record type or dbdict name.

Cannot select from record of type "test."

Cause: The record type entered does not exist as a record in the dbdict table.

Fix: Enter a valid record type or dbdict name.

Cannot initialize record of type "slas."

Cause: On the Usage tab, Query for Records of type has an invalid record type entered.

Fix: Enter a valid record type or dbdict name.

Invalid selection query:
agreement=$G.test.

Cause: On the Usage tab, an invalid field name was used in the Query for Records statement.

Fix: Determine and use the correct field names in the statement.

Wizard "test" does not exist. Contact your System Administrator.

Cause: An invalid wizard name was entered on the Next Wizard tab. When a nonexistent wizard evaluates to true, the wizard workflow will be caught in an infinite loop and the session thread will be killed.

Fix: Enter a valid wizard name on the Next Wizard tab.

Display application could not find screen.
Query=screen.id="wizard.test.me" and language="ENG"

Unrecoverable error in
application: se.call.process on panel call.rad.1

Display application error exit has been taken. $L.ds.ids=L.ds.desc=

Cause: An invalid display screen name was selected on the Usage tab.

Fix: On the Usage tab, enter a valid display screen name or leave the field empty for the default option.