-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Salesforce connector runs out of memory #11580
Comments
Hi @amatasci, Thanks for flagging this issue. Could you please let us know what's your current plan for function app? And to address out of memory issue you can update the function app plan to Premium app service plan. |
Hello, we have a Dynamic / Y1 plan, this is the default one created during the deployment of the connector. |
@amatasci, Do you able to upgrade from below shared one ? - |
@amatasci - |
This possibility isn't available, all options are grayed out |
@amatasci, Is the raised support case are still open? Actually, this upgradation for existing app service needs to be check by the function app team. |
No, MS support closed it because they said it's not a Function App issue |
@amatasci, You can follow the below shared doc to create a function app manually by selecting the plan according to your requirement:- Please go through the below doc for Function App plans with pricing details: - Additionally, To custom deploy this template :- b. Select it and past the above ARM template content in custom deployment page :- Note that, Please do change the function app name while deployment of function in same resource group where old fun app has been already deployed to avoid the existing function override. Once this function app gets deployed successfully, kindly monitor the logs flow and let us know if you get error. Many thanks! |
Describe the bug
Depending on the amount of events to ingest, the Salesforce Function App can run out of memory and stop ingesting audit events
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The function app should ingest all events regardless of the number and without running out of memory
Screenshots
The text was updated successfully, but these errors were encountered: