Pharos Error Generator?

Everybody hates errors and usually has plenty of them to deal with on a daily basis. However, as luck would have it, when you need to create an error on demand it's not so straightforward. We've tried plenty so you don't have to waste your time.

To make it easier on you and your org we have built a tool to help create fake errors. We hope you enjoy it and experiment with it to see all flavors of errors and their respective Pharos Log and Issue views. After generating an error you can then navigate to the generated logs to view to see the debug details.

What's in the Error Generator Package?

Pharos Error Generator is an unmanaged package that comes with some apex code and flows. These bits of logic are "fake", or not real in a a sense that they don't actually do anything meaningful other than generate runtime errors for Pharos to catch.

Pharos Error Generator also comes bundled with a logging framework called Triton that you can play with. If you are a developer, check out the code for Log class and the corresponding comments.

Feel free to peruse the documentation for Triton here.

You can always remove this Error Generator package later if needed. So, let's create some errors!

Installing the Error Generator Package

Before you proceed with this, please make sure you have already installed and configured Pharos.  Initial setup instructions can be found here. 

You'll also need one of the package install links, depending on where you have Pharos installed:

• Production Install Link
• Sandbox Install Link

Please refer to the video below for detailed installation steps:

Using the Error Generator Package

There's not really a prescribed way of utilizing this application. Feel free to generate multiple types of errors to see the different debug views and automated categorization and fingerprinting in action. If you create multiple errors of the same kind, they will get aggregate under the same Issue. Definitely have a look at that Issues tab. If you can, try to wait between button presses as the info panel may show the wrong Log link. The error logs will still generate but that may not get accurately reported on the Error Generator page.

Some of the errors may take a bit of time to generate, like bulk API failures. If you're unsure whether or not a log was created you can always check the Logs tab. Other than that, have fun!