사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/phatnt95/salesforce-apex-agent --skill apex-async-integration시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Apex Async & Integration
Decision tree
- Small deferred unit of work -> Queueable.
- Very large data set -> Batch Apex or an external bulk-processing mechanism.
- Time-based execution -> Schedulable, usually delegating to Queueable/Batch.
- Legacy/simple async requirement ->
@futureonly when its constraints fit; do not introduce it by default. - Event-driven decoupling -> Platform Events / Change Data Capture when appropriate.
- External HTTP callout -> Named Credential / External Credential plus an async boundary if the invocation context cannot perform a callout.
Queueable
- Pass only serializable, bounded state.
- Avoid chaining indefinitely.
- Design idempotency when retries or duplicate execution are possible.
- Make failure handling observable.
Batch
- Choose batch size deliberately based on query shape and per-record work.
- Keep each execute scope independently safe.
- Avoid stateful mode unless accumulated state is necessary.
- Make finish behavior explicit.
Callouts
- Use Named Credentials/External Credentials for authentication.
- Set timeouts deliberately.
- Validate response status and payload.
- Avoid logging secrets or sensitive payloads.
- Define retry policy only for transient failures; do not blindly retry permanent validation/authentication failures.
- Design idempotency for operations that can be retried.
Failure model
Document:
- transient vs permanent errors;
- retry count/backoff;
- dead-letter/manual recovery path;
- transaction rollback behavior;
- user-visible status;
- monitoring/logging.
