Skip to content

jamessimone/apex-async-processor

View on GitHub ↗Related repositories →

Abstract away which async framework is being used within Salesforce in favor of dynamically using the most appropriate solution for the problem at hand.

active 2023-10-202026-01-23 (UTC)

Partial coverage19,450 / 25,066 hourly files (78%) · 2 absent upstream · 5,613 failed, retryable2023-10-032026-08-12 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
17
Pushes
2
Pull requests
2
Issues
2
Stars
3
Forks
2

Activity over time

Daily event counts in the loaded window

Line chart, 827 days from 2023-10-20 to 2026-01-23. Pushes: 2 total, peak 2 in a day. Pull requests: 2 total, peak 2 in a day. Issues: 2 total, peak 1 in a day. Comments: 2 total, peak 2 in a day. Stars: 3 total, peak 1 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
jamessimone6201
ehsky5021
Anuja-dadheech201000

Recent activity

Latest issues, pull requests and releases

  • Pull request#6ehsky2025-07-10 22:08
  • Pull request#5ehsky2025-07-10 21:38
  • Issue#4ehsky2024-08-18 22:26
    How to test from trigger when new queueable job is created? Issue on 101 record and beyond.
  • Issue#2Anuja-dadheech202024-03-03 15:51
    Issue encountered with Database.countQuery() and ORDER BY filter

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 3 stars here means stars gained during the window, not the repo's star count.