Program Errors vs Exceptions

This section uses the term "error" broadly to encompass all the problems you may experience with your Flow system. Errors generally fall into one of two groups being program errors and exceptions.

Errors and exceptions are both saved into the Log that is created when the Action executes. These may also be sent as an Email Notification depending on your Flow configuration.

Program Errors

TIP

Program errors are where the problem is not anticipated

Program errors are where the configuration of the Flow system, or the Flow application itself is failing. These types of errors generally need to be resolved by your system administrator. When you encounter a program error you need to bring it to the attention of your system administrator. These errors may require the involvement of your network administrator if the problem is caused by changes to your network environment.

An example of a program error is a failure to connect to a SQL database because the login credentials have changed. Another example is the failure to send a file to a trading partner because the Internet has gone down.

Persistent program errors

A persistent program error requires the involvement of the system administrator to resolve the issue. The error is considered persistent because it will continue to occur until someone resolves the issue. In the above example the SQL database login credentials changing is a persistent error which will only be resolved once the system administrator updates the Flow configuration with the latest login credentials.

Non-persistent program errors

A non-persistent program error is one that will resolve itself in time. These errors can generally be ignored safely, but should be monitored to ensure they have resolved themselves. In the above example the failure due to the Internet going down is a non-persistent error (if the Internet has gone down due to external reasons). In this case the Action will process successfully the next time it executes so long as the Internet has come back up.

Over time you will come to recognise the sorts of errors occurring for your Flow system that are non-persistent. Generally if the error notification is received repeatedly then it is a persistent error. If you are in doubt you should contact your system administrator.

Exceptions

TIP

Exceptions are errors that have been anticipated to occur.

Your Flow configuration is performing tests of the data as it processes and if a test fails this is known as an exception. An exception will generally be reported in an easy to understand manner allowing the operator to resolve the issue and resume or restart the processing. The operator should have appropriate training to be able to deal with exceptions themselves.

An example of an exception is receiving an order which contains a stock code that does not exist in your system. This may be reported as "Stock item "ABC" does not exist in your financial system - please either add the stock code or contact the provider to correct the stock code they are sending you". Operators would normally have appropriate training on the company processes so they know how to handle the exception.

Once the exception is resolved in line with the company processes the Flow system can reprocess the order