function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
Andy S.Andy S. 

Callout governor limits from Triggers. Clarification desired.

As stated in the Apex Code Developer's Guide, governors and limits section, there is a limit to the number of "@Future" method calls: " also imposes an organization-wide limit of 200 method calls with the future annotation per license per 24 hours."


Also, as stated elsewhere (though I don't have an immediate reference), callouts performed by a Trigger must be done using an @Future method call.



1) Am I correct in understanding that if trigger-based callouts are desired, there is therefore a limit of 200 callout notifications per 24 hours?


2) Can someone clarify if this is 200 callouts executed by any single individual user license?  Or is it similar to other limits where, for example, if there are 20 licensed users in the Org, the actual limit is 20*200 = 4000 (per 24 hours)?


3) I may be mis-using the intended purpose of triggers and callouts, but my intention is to notify an external server when critical changes are made to a particular object.  Given such changes may occur based on end-user browser actions., it's possible that 200 separate changes are made in one day.  If I am interpreting the above limits correctly, the 200 value seems fairly low, relative to the other Governor limits.

- Am I mis-using the intended purpose of trigger-based callouts?

- Is there a better method of scheduling such callouts?  (I could bulkify the callout to provide notice of multiple changes at once, but that doesn't work for 200 individual end-user changes.)