New answers tagged

0

Limits Class will always run in the same namespace it is being run from. So, the limits it returns will be of the same namespace limits and does not include any other namespace limits. However, you can go to Salesforce developer console > Debug > Change log levels > Add/Change for General trace and set all levels to none but profiling to INFO or ...


1

You can use sfdx force:limits:api:display


1

After a quick check to Setup -> Environments -> System Overview, I see that the API usage has been exceeded (which was very unexpected and not caused by my development efforts): I guess the lesson here is that force:source:deploy consumes API calls


0

There are many fields available on permissionset object. You can query those permission which you need. In general:- PermissionsPermissionName One field for each permission. If true, users assigned to this permission set have the named permission. The number of fields varies depending on the permissions for the organization and license type. read more ...


1

Limits apply to a transaction A batchable execute() is a transaction. There are 0..n execute transactions per batch depending on the number of sobjects returned in the start() method and the size of the scope parameter when the batchable is invoked (default is 200, min is 1, max is 2000). So, if you had 10,000,000 leads and scope was default 200, you would ...


1

It depends on how you structure your batch. If you put the DML Operations in your execute method, then you are using the interface and chunking appropriately, so you would only process 200 records at a time (or some other number if you change the batch size). The maximum batch size is 2000 records, so you would still not be able to increase it to the point ...


1

You are on a very old version of the connector that should be upgraded at the soonest opportunity. Additionally, if you have a bulk load, the most reliable way of injection is to create a DE in Marketing Cloud and use a DE entry event. Doing large batches is not a reliable method for injection. Once your CRM instance has custom apex processing or other ...


3

Queueable Apex is an asynchronous context as far as limits go, which does affect a variety of limits, including the total SOQL count (200 instead of 100). Each Queueable job enqueued and executed represents a separate transaction, which is the unit of limits consumption. What is happening here appears to be your process automation downstream of the ...


1

Unfortunately there is no general answer as is stated in the quote you posted: If multiple flows are triggered or your org has custom logic generating transactions with more than 2,000 records, the flow invocation fails. So in theory you could upload 2,000 records at once. This applies only if your journey trigger is the only flow/logic that is invoked. ...


4

You can only enqueue one job from a job (be it Batchable or Queueable). There are pretty much exactly two reasons you would run into this error. Either XFTY_DummySObjectSupplier kicks off a Queueable, or the object you are creating data for has triggers which do the same. Regardless of which is the cause, you are going to hit a roadblock in that you can ...


3

Open Debug > Change Log Levels. Set the debug level of profiling, apex as fine. Check below: (Also better to set expiration to 11.30pm) Now, when you get log, open it and open Debug > View log panels. and select Execution log and execution overview. you will see as below: Here you can see count of each query and time taken and other things. If ...


2

Use Profiling. By going in to the Developer Console, you can go to Debug > Change Log Levels, then modify the debug logging to include "Profiling" set to "FINEST". From there, run your execution, and afterwards, you'll get a section in your debug logs that show you which queries were executed, and how many times. For example, here's an example from my dev ...


3

Its called as boxcarring, Salesforce bundles multiple request in to 1 to save repeated calls to server. You can seee from Debug logs, only one is created. A quick solution is to add a timeout or use the promise chain while calling apex. In this way , each apex call will be treated as new transaction and those limits get reset. new Promise(function(resolve,...


-1

Have a static integer as a counter in each class, and increment it whenever a query is made. This way you can have the count.


6

Aura, and LWC, groups several requests together in order to maximize performance. This is called "boxcar'ing" (or boxcarring) in the documentation. All Apex requests in the same boxcar payload are subject to a single set of governor limits, even though they're allowed to fail/succeed independently. This means you need to make sure you don't place DML before ...


-1

That depends on which objects you are updating, and how you have written triggers. If you think you can bypass the execution of trigger after a dml, then please do bypass. This avoids trigger recursion. Also make sure process builders are not executing multiple times and workflows as well. To avoid multiple execution of process builders and workflows, have a ...


Top 50 recent answers are included