Troubleshooting and Error Handling in Forgeworx Pro
If this is your first time with Anvil Forgeworx Pro™, please see our Quickstart Documentation before proceeding.
All inputs will be made in the configurator screen; a walkthrough to this screen may be found here.
There are two types of errors that can occur in Forgeworx:
- Application Errors
- Configuration Errors
An application error usually occurs when communication between the client and server is degraded. There are three errors of this type that are the most common:
- 'LoadProject exception error' – This error happens if the project browser UI is trying to display a large amount of data to the user or the time to load the project is very long due to a slow connection to the server
- 'SaveProject exception error' – Occurs when a large amount of data is being saved or there is a degraded connection to the server during a save. Can also happen in an unhandled error state where bad data gets generated by the configurator
- 'PulseError' – The Forgeworx server sends a signal to the client every thirty seconds to verify the user is still logged on and the session active. Two missed signals in a row will cause the session to close and a license returned to the pool. This is a sign of a slow internet connection.
*Note the pulse error is different than a session timeout, which is currently set at 30 minutes.
Configuration errors occur when Forgeworx cannot return a valid assembly. There are handled and unhandled errors.
A handled error takes place when the user attempts to enter an invalid input and Forgeworx cannot return a valid assembly. As an example, do the following:
- Enter the configurator
- Support type = Vertical Hanger
- Existing Beam = True
- Load = 98501
This error was returned because the maximum load of a standard single rod assembly is governed by the Fig. 55 structural attachment, with a maximum load of 98500 lbs:
- Load = 98500
- Existing Steel Elevation = 144
- Vertical Movement = .5
The hanger components are removed because Anvil does not supply a standard spring or constant that is rated for a load of 98,500 lbs.
This behavior is how Forgeworx deals with handled errors. It will remove components of the hanger assembly, disable outputs, and return an error message.
Exiting to the project browser will save the data in the error state. A sketch or model will not be returned in a batch output for this hanger.
You can change the data to a valid value in the configurator or in the project browser.
There is no validation for values of input data in the project browser, only data type. If you enter the configurator in a handled error state, troubleshoot the configuration until a valid hanger is returned or contact Anvil for assistance here (LINK)
An unanticipated error inside of the configurator is an unhandled error. It is designated as unhandled because the application has not been designed to "handle" this error state. There are a near infinite number of permutations for configuration options, pipe size, component size etc... and unanticipated configurations will cause an unhandled error. As the application matures, the instances of unhandled errors will approach zero.
Unhandled errors usually occur when the user attempts to configure a hanger at the support assembly level, and then changes a parameter at the hanger mark number level. As an example, selecting a beam clamp as a structural attachment type then increasing the load beyond the maximum allowed for that clamp is a typical workflow that could cause an error. The message "An ETO client error has occurred, returning to project browser" is displayed.
The user is then prompted to save or cancel the hanger configuration. In most cases, the unhandled error state cannot be recovered by changing inputs because it is usually triggered by an input or series of inputs that cannot be repeated in the project browser. If the user chooses to save the hanger by hitting OK, most of the time the hanger must be deleted and re-started.
This is why whenever possible, data should be entered into the project browser. Data entered into the project browser is automatically saved and should an unhandled error occur, it can always be retrieved. This way, only edits made in the configurator will not be saved, and the bulk of the information remains intact.
Back to top