Salesforce Support created a known platform issue for the problem that ruined our solution
https://issues.salesforce.com/issue/a02Ka00000eOn7C/
The ETA for the fix is the mid May which is too late for the hackathon results submission.
I am now working hard on workaround using Agent API instead of direct access from apex class
Log in or sign up for Devpost to join the conversation.