Schedules & Queues
Verified 2026-07-07 · EventBridge Scheduler group
default· 20 schedules total
Production Schedules (the sync heartbeat)
Section titled “Production Schedules (the sync heartbeat)”| Schedule | Target function | Cadence (ET) | Purpose |
|---|---|---|---|
prod-loadtenant-information | prod_getTenantInfo | daily | Enqueue one SQS message per active tenant → triggers prod_jbwextraction |
Prod-installed-equipment-sync | prod_getTenantInfo | daily | ⚠ duplicate of the above — both enabled |
prod-createJBAgreements | prod_jbwservicetitansagreementspull | daily | Auto-create JBW agreements from staged data |
prod-agreement-sync-with-st | prod_jbwagreementslocationsstupload | cron(0 5-10 * * ? *) — hourly 5–10 AM | Write agreement references back into ServiceTitan |
Prod_claims_update_JB | prod_jbwclaimsstupdate (input bulkUpdate:true) | daily | Pull claim statuses from JBW |
prod_pendingclaims | prod_jbwpendingclaimstoredproc | daily | Pending-claims stored proc |
prod-datatransformation-schedule | prod_jbwequipmentsyncstoredpro | daily | Equipment data transformation stored proc |
prod-installed-equipment-datatransformation | prod_jbwequipmentsyncstoredpro | daily | ⚠ duplicate of the above — both enabled |
prod-agreement-sync-from-jb | prod_jbwdatapullfromJB (input dateFilter:true) | daily | Reverse sync: JBW agreement status → DB |
prod-remove-agreement-tags | prod_jbwagreementreferenceremovalfromst | daily | Clean JBW references off ST locations |
prod-businessunit-datapull | prod_jbwtenantbusinessunitsdatapull | daily | Business-unit refresh (no repo source) |
prod-workizdatapull | prod_jbwworkiztenantifno | daily | Workiz tenant pull (no repo source) |
prod-workizdatapush | prod_jbwworkizjobdatapush | daily | Workiz job push (no repo source) |
EmailPendingData | prod_jbwdealerpendingagreementsclaimsnotification | daily | Pending agreements/claims email (SES) |
Dev/Stage Schedules
Section titled “Dev/Stage Schedules”| Schedule | Target | Cadence | State |
|---|---|---|---|
loadtenant-information | dev_getTenantInfo | hourly (CT) | enabled |
datatransformation-schedule | dev_jbwequipmentsyncstoredpro | every 15 min (CT) | enabled |
dev-Workiz-data-pull | dev_jbwworkiztenantifno | every 15 min | enabled |
claims_update_JB | dev_jbwclaimsstupdate | hourly | enabled |
dev_pendingclaims | dev_jbwpendingclaimstoredproc | daily | enabled |
dev-createAutoAgreements | dev_jbwservicetitansagreementspull | every 30 min | disabled |
SQS Queues
Section titled “SQS Queues”| Queue URL | Consumer (event source mapping) | Batch | Visibility | DLQ |
|---|---|---|---|---|
https://sqs.us-east-1.amazonaws.com/660537473428/prodtenantList | prod_jbwextraction | 5 | 1200 s | ✅ ProdFailedMessages (maxReceiveCount 10) |
https://sqs.us-east-1.amazonaws.com/660537473428/tenantList | dev_jbwextraction | 10 | 1800 s | ❌ none |
https://sqs.us-east-1.amazonaws.com/660537473428/prodWorkizTenants | prod_jbwworkizjobsdatafetch | 10 | 900 s | ❌ none |
https://sqs.us-east-1.amazonaws.com/660537473428/stgWorkizTenants | dev_jbwworkizjobsdatafetch | 10 | 900 s | ❌ none |
https://sqs.us-east-1.amazonaws.com/660537473428/ProdFailedMessages | — (DLQ) | — | 30 s | — |
All queues were empty at inspection time. All four event source mappings are Enabled. Note the correct ordering on prod: queue visibility (1200 s) > Lambda timeout (900 s).