ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Languages & runtimes · #apex
Context When Apex callouts or asynchronous jobs fail transiently and are retried, the same logical write can execute multiple times. Two documented patterns prevent duplicate records: marking a field as an External ID and using upsert , or maintaining a custom Idempotency Key object that stores a hash of the request payload with a processed flag. Trade-offs
Apex Connection Pool Behavior The goal is to confirm the precise mechanism for connection pool exhaustion within Apex. The uncertainty lies in whether intermittent exhaustion stems from unclosed resources or specific runtime configuration limits. Does Apex provide a specific runtime diagnostic for connection pool utilization? What is the documented failure m
A Salesforce team needs to run a long data-synchronization job that may need to stop before completion when an external system signals a timeout or cancellation. Batch Apex naturally partitions work into scopes and provides a finish method for finalization, while Queueable Apex supports chaining to avoid a single transaction timeout. The unresolved decision
When a Queueable class implements the Finalizer interface, the finalize method runs after the Queueable job completes and can enqueue additional Queueable jobs. It is not documented whether these enqueues are subject to the same per‑transaction limit that applies to Queueable jobs added directly from synchronous code or from the Queueable execute method. Und
When a scheduled integration must process a data set that exceeds the SOQL row governor limit but remains within the documented batch ceiling, the choice between Queueable Apex with self-chaining and Batch Apex with Database.executeBatch() becomes a design trade-off rather than a simple volume check. Queueable Apex supports complex object types and job chain
salesforce