Jobvite Operational Status Page

May 29, 2026

Current Status: Still Investigating Some newly posted job requisitions are not appearing on certain external career websites. While positions are being created successfully, they may not consistently publish to specific branded external sites. Customer Impact: Candidates may be unable to view recently posted job opportunities on affected external career sites. At this time, there is no reliable workaround to force affected postings to appear. What We Know: Job data and listings are being generated correctly within the system. Some external career sites are not displaying the most recent postings. Next Steps: We are still actively investigating the issue and working to identify the root cause. We will provide the next status update within 2 hours or sooner if additional information becomes available.

May 26, 2026 · resolved May 26

The issue impacting analytics data delays in Production has been resolved. Data syncing is currently in progress; however, it may still take additional time for all records to update and reflect the latest information fully. We are closing this incident, but please allow time for the synchronization process to complete. An RCA will be available within 7-10 business days

Apr 8, 2026 · resolved Apr 8

**Date:** April 8, 2026 **Duration:** ~11 hours \(01:00 am ET – 12:00 pm ET\) We want to share an update on a recent automation issue, including what happened, how it was resolved, and the steps we’ve taken to prevent it from happening again. ## Customer Impact On April 8, 2026, certain background processing agents responsible for moving data between Talemetry Apply and external Applicant Tracking Systems \(ATS\) were not running as expected. As a result: * Job and application data imports/exports were delayed. * Job status updates were not reflected in near real time. * Newly submitted applications were not immediately visible in the external ATS. No data was lost. All affected jobs and applications were successfully processed once service was restored. ## Root Cause The issue occurred due to a congestion condition in the Mukmuk agent processing system: * A large number of agents were scheduled to run, exceeding the capacity of the background worker pods, which were actively handling the workload. * Several non-essential agents consumed capacity, blocking higher-priority production agents, and causing the system to enter a stalled state where critical agents could not execute. In short, the system lacked sufficient safeguards to prevent inactive or non-critical agents from interfering with production workloads during peak processing conditions. ## Resolution Once the issue was identified, the following actions were taken: 1. Non-essential development agents were disabled. 2. Background processing capacity was temporarily increased to accelerate backlog processing. 3. Queued jobs were monitored until all pending imports and exports completed successfully. By approximately 12:00 ET, all agents had caught up, job processing returned to normal, and customer-facing data reflected up-to-date timestamps confirming restoration. ## Preventative Actions To reduce the likelihood and impact of similar incidents in the future, the following improvements are underway or completed: * **Proactive Monitoring** * New alerts are being added to detect stalled or non-running agents in near real time. * Monitoring schedules are being expanded beyond limited overnight checks. * **Improved Observability** * Additional metrics will track agent execution health and backlog growth. * Engineering alerts will trigger automatically when agents fail to run as expected. * **Operational Safeguards** * Cleanup of unused or churned agents to prevent resource contention. These actions will significantly reduce detection, diagnosis, and recovery times should similar conditions arise again.

Mar 26, 2026 · resolved Mar 26

This incident has been resolved, data is verified to be available in Analytics tools in the expected data sync time frame.

Mar 12, 2026 · resolved Mar 13

This incident has been resolved. All delayed emails have been successfully reprocessed, and new emails continue to be processed successfully. An RCA will be provided within 7-10 business days.