You need to sign in to do that
Don't have an account?
MernaE
Lightning Process Builder Breaks Deployment
We defined a Process Builder on the Lead object and ran all unit tests successfully in production. However, during the deployment, all the unit tests that were creating a Lead record failed with the following error:
System.DmlException: Insert failed. First exception on row 0; first error: CANNOT_EXECUTE_FLOW_TRIGGER, The record couldn’t be saved because it failed to trigger a flow. <br>common.exception.AssertionException: ORA-20070: Cannot read from apex_class and apex_trigger while running tests ORA-06512: at "SNEEZY.ASSERT", line 11 ORA-06512: at "SNEEZY.ASSERT", line 41 ORA-06512: at "SNEEZY.CAPEX", line 3095 ORA-06512: at "SNEEZY.CAPEX", line 3088 ORA-06512: at "SNEEZY.CAPEX", line 194 ORA-06512: at line 1 SQLException while executing plsql statement: {call cApex.get_classes_blk_nc(?,?,?,?,?,?,?,?)}(00DA0000000byvR, [ null ], [ null ], [ EXCLUDED (18) ], EXCLUDED, EXCLUDED,
We had to deactivate our process and then ran a deploy to work around this issue.
Based on some posts in the forum (https://developer.salesforce.com/forums/ForumsMain?id=906F0000000B5zB" target="_blank), we are not the only ones experiencing this issue. Support has been unavailable for this issue, because we are "standard" customers, even though it's clearly a platform bug. Please help!
System.DmlException: Insert failed. First exception on row 0; first error: CANNOT_EXECUTE_FLOW_TRIGGER, The record couldn’t be saved because it failed to trigger a flow. <br>common.exception.AssertionException: ORA-20070: Cannot read from apex_class and apex_trigger while running tests ORA-06512: at "SNEEZY.ASSERT", line 11 ORA-06512: at "SNEEZY.ASSERT", line 41 ORA-06512: at "SNEEZY.CAPEX", line 3095 ORA-06512: at "SNEEZY.CAPEX", line 3088 ORA-06512: at "SNEEZY.CAPEX", line 194 ORA-06512: at line 1 SQLException while executing plsql statement: {call cApex.get_classes_blk_nc(?,?,?,?,?,?,?,?)}(00DA0000000byvR, [ null ], [ null ], [ EXCLUDED (18) ], EXCLUDED, EXCLUDED,
We had to deactivate our process and then ran a deploy to work around this issue.
Based on some posts in the forum (https://developer.salesforce.com/forums/ForumsMain?id=906F0000000B5zB" target="_blank), we are not the only ones experiencing this issue. Support has been unavailable for this issue, because we are "standard" customers, even though it's clearly a platform bug. Please help!
To receive notifications on the progress of the fix, go here (https://success.salesforce.com/issues_view?id=a1p300000008YVj) and click the button "This Issue Affects Me"