IC2 is not aware of BatchApexErrorEvent standard object and its fields

[Alan Birchenough]

In the course of completing my certification maintenance exam I was required to create a trigger on the BatchApexErrorEvent object, which is new in Summer '19. IC2 is unaware of the existence of this object, so in order to create the trigger I had to use the Developer Console and then subsequently retrieve the trigger into the IC2 project. And since the BatchApexErrorEvent object and its fields remained unknown to IC2 throughout this process even after OST refresh, they continued to show up as unresolvable symbols in the editor.

[Scott Wells]

Alan, I have that SObject in my offline symbol table:

Can you verify that the OST for this project is based on the latest API version and up-to-date?

[Alan Birchenough]

I was on version 46.0. I will do a total regeneration and see what happens.

[Alan Birchenough]

D’oh. It is there after the third regeneration. I don’t get why it wasn’t there the first and second time, but I guess it’s not worth a lot of effort to investigate. I probably can’t reproduce the problem anyway.

[Scott Wells]

I'm going to resolve this, but if you do find that you run OST generation and don't see this object again, please let me know so we can grab some logs and see what's going on.

[Alan Birchenough]

Fair enough. Thanks.