Is Gem down?

We're aware of an issue affecting data syncs and webhooks for teams using the Workday integration. Since June 16, 2026, some pipeline metrics have not updated as expected, which may appear as missing or out-of-date recruiting data in affected accounts. We've identified the root cause and are deploying a fix. No data has been permanently lost. Once the fix is in place, we'll rebuild the affected metrics from your source data and reporting will return to normal. We'll post another update as soon as the fix is complete. Thank you for your patience.

The underlying issue has been resolved and Workday syncs are now running successfully again. Both full and partial syncs have resumed across affected accounts. We're now waiting for these syncs to finish processing so your recruiting data is fully up to date. Until they complete, you may still see some metrics that haven't refreshed yet — this is expected and will resolve on its own as the syncs catch up. We'll post a final update once all data is current.

This incident has been resolved.

We are aware of an issue with sending e-signature (offer) requests through Gem. This is caused by a Docusign outage that is currently being worked on. Please check for updates on Docusign's status page and try again after the issue is resolved: https://health.docusign.com/ We will continue to monitor the situation and share updates here.

Docusign has resolved the outage with their services, and Gem e-signature and offer requests are now working normally.

We are currently investigating an issue affecting some users' ability to send sequences. Users may see an error message stating "Your changes were not saved because this sequence was edited elsewhere." Our engineering team is actively working to resolve this. We will provide an update as soon as possible.

The issue affecting sequence sending has been resolved. If you were seeing the error "Your changes were not saved because this sequence was edited elsewhere," please refresh your browser — sequences should now send normally. We apologize for the disruption.