Josh Kaplan the Apex Product Manager gave quite a detailed blog post on this new governor entitled Script Limits, Begone!. In it he states this...
What does this CPU timeout include? We are only counting things that require application server CPU use. For example, the time spent in the database retrieving records will not count, nor will time spent ...
Can a Salesforce instance contain 50+ million records? Almost certainly. I've seen instances with millions of records, although none as large as 50 million. A Salesforce sales person would be able to confirm the max size of a table, if there is one. (50 million records will get their attention and you can expect a quick answer.)
Would I recommend Salesforce ...
Being able to store 50M rows in a single organization would require 834 Unlimited Edition licenses, 5000 Enterprise Edition licenses, or 40 500MB "blocks" of additional data storage (or some combination thereof), making storing this amount of data very expensive. Assuming that the organization's soft storage limit was of no concern, hypothetically speaking, ...
QueryMore is the appropriate means of accomplishing this if you're getting data all at once. For pagination, such as in a website or portal, sort by some value then use filters. I would recommend a field with a high cardinality (e.g. many unique values) because it makes pagination that much easier.
I've posted this answer elsewhere, but I'll post it here, ...
You will receive an error message when trying to save files of
Error: The total size of apex code in this application after removing comments exceeds the maximum character size of 3,000,000
and the files will not submit to the server. You can contact your account executive and may be able to open a discussion to add to this limit if it is deemed ...
I raised a case with SalesForce to ask them the same question. After a several weeks I finally got a reply to say:
We have consulted our backline team and they have confirmed that time
will change as they are subjected to CPU availability.
Processors naturally take a variable amount of time to process code,
so it's almost never going to be the exact amount ...
A quick test would suggest that they do...
Here is a simple class in my DE
and the code usage
If I add loads of characters, the usage goes up..
when I removed them, it went back down, now I added loads of white space, and the usage climbed again:
And this is chaining lots of spaces together, so I would say that lots of individual spaces in real code ...
Per the Governor Limits, you can only send 5000 single emails a day (or less, depending on license).
Using the API or Apex, you can send single emails to a maximum of
5,000 external email addresses per day based on Greenwich Mean Time
(GMT). Single emails sent using the Salesforce application don't count
toward this limit. There’s no limit on ...
Unfortunately your test is flawed. What you're missing here is that using the Developer Console uses API calls to the Tooling API (it's a little crazy that these are counted, I know)!
The API call limit includes inbound calls only. Outbound calls (i.e. callouts) are only governed by the per transaction and maximum timeout limits.
The Salesforce Developer ...
There are no technical restraints regarding the ten object limit. This is actually mentioned in the documentation somewhere. However, if salesforce.com finds out (however that may be), you would be in violation of your contract and at risk for contractual breach.
In theory, this means you'd be forced to pay for the more expensive licenses that you would ...
Looks like there's some concrete documentation as of API v49.0 (Summer '20). The documented limit is 16,384 bytes.
The recommendation is to limit the URI to 2000 bytes, and headers to 8000 bytes.
Re-ran my code here, and came up with a limit of 16057. Looks like this number might vary from release to release, between pods, ...
@RestResource annotated apex classes are just like normal apex class and only difference is they expose the apex class as a HTTP GET,POST,PUT or PATCH web-service and hence all the governor limits applicable to the apex class context apply here .
These limits will be 50,000 queries in a context,150 DML,100 SOQL limit of context ,CPU limit ,Heap size limit ...
I'm sure metadata does not count towards the storage limits, only the records stored inside those custom objects that maybe created. I doubt this is actually documented anywhere so the easiest step might be to file a case with support and send the response to the client.
Posted a link to the success community to try and speed things along, this might help:
As you are chaining the jobs you have limit of 1 on child jobs.
When chaining jobs, you can add only one job from an executing job with System.enqueueJob, which means that only one child job can exist for each parent queueable job. Starting multiple child jobs from the same queueable job isn’t supported.
See here under queuable Apex limit section:
You can use a HAVING clause:
AggregateResult results = [SELECT COUNT(Id) sum, Tool__c Id FROM Gear__c WHERE Tool__c = :tools GROUP BY Tool__c HAVING COUNT(Id) > 1];
This will give you a list of AggregateResult objects where the sum and Tool__c Id are given. You can even use the Map trick to get the count per record easily:
Batches don't run until stopTest(), and stopTest() restores the test method's limits after the batch executes before it returns. This means that your test method will never see that limit set unless it sends an email itself (which, of course, will never be delivered/sent).
You have two ways to handle this:
Don't bother with the assert. Assuming the email ...
It sounds like you've ran into your API Limit for the 24-period.
Check this. Go to Setup and then click System Overview
You API Usage will be on the top right. If you are at your maximum, I suggest calling Salesforce-Support immediately, and ask to get your API Limits increased temporarily. SF-Support is generally friendly and will usually grant the ...
You'll need to clean up your code. The 3,000,000 character limit is the universal limit for any namespace. I've found that the typical code base can be optimized by at least 50%.
Delete all your unit tests (or comment them out). Then, start writing use-based unit tests, covering each page, trigger, etc that you know you need. Then, review the ...
As a best practice, don't exceed 10,000 child records for a master-detail relationship.
Refers to record relationships, thus it is refering to a parent record with the number of related child records not exceeding 10,000. Thus it means 'per Master' record.
Here is my attempt to combine all of the answers given, and to interpret the SF Documentation provided on email limits.
A SINGLE_EMAIL_LIMIT_EXCEEDED exception is thrown when the daily Messaging.SingleEmailMessage limit is exceeded. This exception can be thrown in other cases as well, like when email deliverability is not set correctly.
This is still valid, have a look at the System overview area of your org and you will see there is an indicator bar (shown in screenshot) that details the information you are talking about. I can verify this org has 14 custom objects and 2 custom settings (it is a throwaway dev org of mine I use for playing around in). 16/400 is also exactly 4%.
Custom settings are cached in a special application layer cache which allows a developer to access this data without performing a query, similar to how a CPU's cache allows it to access frequently accessed information without requesting the data from main system memory.
All custom settings are cached, and each record in the cache counts towards the 10MB/1MB-...
Because you wait until the execute() method to query for the records to delete, you are not utilizing the scope parameter (the second parameter of the Database.executeBatch method--'200' in your case) to limit the size of your batches. Because of this, you are attempting to delete too many records of too many types in a single call. If three different ...
When you say 997, it runs 998 times counting initial call (actually not hidden)
The call to the class constructor
This can be tested in Dev console > open log > Debug > View log panels > Execution Overview > Executed Units
See the documentation.
You can list up to 250 IDs per email. If you specify a value for the targetObjectIds field, optionally specify a whatId as well to set the email context to a user, contact, or lead. This ensures that merge fields in the template contain the correct data.
Personally, I know of implementations with 100M Tasks--Watch http://wiki.developerforce.com/page/Webinar:_Extreme_Salesforce_Data_Volumes_(2013-Feb) Next, how about loading 20M records in 1 hour? http://events.developerforce.com/en/events/webinars/bulk-api
Yes you can do this using chatter. Check here Upload a File as Large as 2GB in Salesforce Using a Visualforce Page
Basically what you need to do here is include chatter component in the VF page and then using some CSS display it and attach file of 2 GB.
<chatter:feed entityId="<ID of the custom object record>" />
If more requests are made while the 10 long-running requests are still running, they’re denied.
Salesforce allows you to have a limit of 10 long running requests per ORG, where long running requests are defined as processes taking over 5 seconds. Once you have reached the limit of 10, Salesforce will block any other Apex request until one or more of the 10 ...
You're pretty close to a solution with your parent-child subquery.
The big thing to realize is that, similar to how adding parent__r.someField__c gives you a real SObject instance nested in your query results, a parent-child subquery gives you a List<SObject> nested in your query results.
About the only thing I'd add is to limit the subquery rows to ...