[SalesForce] Catch System.AssertException

Is there a way to catch System.AssertException?

For example, some class is known to throw assertions in certain cases and it's ok to deal with that on some upper level. But unfortunately straightforward try-catch doesn't work for assert. I expect that this code will not throw an exception but it does:

try{
    System.assert(false, 'fail');
}catch(System.AssertException asEx){
    System.debug('success');
}

So, is there a way to implement ability of catching asserts?

Best Answer

Short answer no.

From the Apex Developers Guide:

Asserts that condition is true. If it is not, a fatal error is returned that causes code execution to halt. The returned error optionally contains the custom message specified in the last argument.

You can’t catch an assertion failure using a try/catch block even though it is logged as an exception.

You'll need to convert your asserts to exceptions if you want to handle them either at the point that they are thrown, or in any calling code.

Related Solutions

[SalesForce] throw an exception in apex and still log the caught exception

First please take a look at this answer for a partial solution / approach, Can I prevent an insert to be rolled back even if my class (later) runs into an exception?.

Basically as per the Apex Developers guide the final commit transaction management is baked into Apex, meaning it will always rollback if you let the platform handle your exceptions, if you don't you have to manage the rollback scope yourself or accept any DML that has been issued be committed.

If the entire request completes successfully, all changes are committed to the database. For example, suppose a Visualforce page called an Apex controller, which in turn called an additional Apex class. Only when all the Apex code has finished running and the Visualforce page has finished running, are the changes committed to the database. If the request does not complete successfully, all database changes are rolled back

The only way to get control of this is to use the try/catch/finally semantics, along with Savepoints, and critically not throwing any exception (note that as per the answer above some system exceptions cannot be caught sadly). Since your implementing the Auth.RegistrationHandler interface your stuck with its method signature and thus cannot code any alternative way to pass errors back, not does there appear to be any support for this on the interface itself.

Passing a null user back from createUser. What happens if you using try/catch/finally with a logging approach as above and then null back? I expect the system will handle this and present some general error message. Of course in this case your more detail errors will have been logged, since technically the call completed successfully. You would of course have to educate your users / admins to check your own log in this case. Given the frequency of the issues, perhaps this is tolerable? As regards the updateUser method, i don't see any way to infer errors with a successful execution of the method.

Summary and System.debug? Sorry this is not the answer you wanted, but i believe this is the situation. Your not the first to want to implement such a logging approach as you can see. Ultimately its a matter of how far your prepared to go against the transaction management semantics of the platform vs resorting to having your Admins enable Debug Logs and adding System.debug output to your code to output messages to the standard platform log that can then be reviewed for your errors.

[SalesForce] Not able to catch exception using try catch block

You have the following line inside the try block.`

List<Database.SaveResult> results= Database.update(listUserDeactivate,false);

The database.update method takes in two parameters as in your code:

The sobject or collection of sobjects to perform the update on
allOrNone - This parameter is set to false to allow partial success

The second parameter called allOrNone is exactly what differentiates the database.update from update. While using the update method and performimg a DML like

update listUserDeactivate;

Then even when the update of any one of the records in the list fails - the whole update process fails and a DML exception is thrown. This would have been in your case too have you written the code as

List<Database.SaveResult> results= Database.update(listUserDeactivate,true);

This sets the allOrNone parameter to true which implies system either updates all the records(i.e. when no individual record update fails) or updates no record(i.e. the scenario where at least the update of one record in the list fails). So what is happening in you case is that because allOrNone is set to false, partial success of the update operation is allowed and that is what exactly happened. Not all records in the list were updated successfully and due to your way of using database.upsert NO EXCEPTION was thrown.

But logs capture everything in finer detail, including the DML update situation of every individual record. Hence the failure is logged in the debug logs. Thanks

Best Answer

Related Solutions

[SalesForce] throw an exception in apex and still log the caught exception

[SalesForce] Not able to catch exception using try catch block

Related Topic