Historique des pannes de Beamery

We are investigating reports that some CRM system-generated emails may be delivered to recipients' spam or junk folders rather than their inboxes. This does not affect outbound candidate-facing emails, which are sending and delivering as normal. We will provide an update as soon as we have more information.

We have implemented a fix for the affected CRM system-generated emails and are now monitoring deliverability to confirm messages are reaching inboxes as expected. As a precaution, we are also carrying out a final sweep to check for any other areas that may have been impacted. Outbound candidate-facing emails remain unaffected throughout. We will confirm once the fix is fully verified.

The issue affecting deliverability of some CRM system-generated emails has been resolved. Our final sweep confirmed no other areas were impacted, and outbound candidate-facing emails were unaffected throughout. Deliverability has returned to normal. Thank you for your patience.

We're currently experiencing a delay in data synchronization in our Sandbox (US) environment due to an issue with one of our database nodes provided by our cloud infrastructure provider. **What this means for you** Features that rely on search indexing — including People Grid, recipes, and related functionality — may temporarily display or operate on outdated data. **Impact** • No data loss is expected. • Updates made during this period are not lost; they will be processed once synchronization resumes. • Other Sandbox functionality remains available and production environments are not impacted. We are actively monitoring the recovery of the affected node, after which data synchronization will automatically resume and catch up on any pending updates. We'll post further updates as the situation progresses. Thank you for your patience.

Data synchronization in our Sandbox (US) environment has been restored and is now processing normally. Any backlog has been fully caught up, and there is no longer any customer impact. Features that rely on search indexing — including People Grid, recipes, and related functionality — are once again operating on up-to-date data. We are continuing to monitor the environment closely while the underlying infrastructure recovery completes in the background. This work is not expected to affect service. Thank you for your patience.

The earlier data synchronization issue in our Sandbox (US) environment has been fully resolved. All services are operating normally, and features relying on search indexing, including People Grid, recipes, and related functionality, are running on up-to-date data. No data was lost during the incident, and all delayed updates have been successfully processed. Thank you for your patience while we worked through this.

Beamery Engineering team has been alerted to an increase in CPU usage in our ElasticSearch cluster, the issue is being investigated. Search results may respond slower than normal.

The team have identified a spike in Recipe usage as the root cause to the increased CPU. Additional resource is being deployed to support the increased load.

CPU usage on the ElasticSearch cluster continues to be high despite remediations, the Beamery Engineering team have made further adjustments to bring this down. Recipe process time is expected to be reduced.

Load is coming down following updates and normal service is expected to resume soon. The Beamery Engineering team are continuing to monitor the performance.

Elastic CPU returned to normal following mitigations, normal service resumed.

Individual Events cannot be accessed via the Events Tab in the Beamery UI at this time. Beamery engineering is actively investigating a resolution to this issue.

Beamery Engineering team has now released a fix for this issue, and access to events UI is now restored as expected.

We are currently experiencing disruptions across our Workday Integration caused by service outages to Workday, specifically affecting the WD3 and WD3 Non-Prod hosts. Our engineering team is actively investigating this issue and monitoring the situation.

As of 03:00 UTC on 14th February, the service outage experienced by Workday is no longer occurring. The Beamery<>Workday Integration is functioning as expected. Please reach out to [email protected] if you have any queries.

We are aware of issues, with candidates being unable to login to the Candidate Portal, we are currently investigating.

We have identified a fix, this has been deployed and tested and we can confirm that the issue has been resolved.

The Cloudflare outage has been restored and Beamery Sandbox US is back online.

Cloudflare have implemented a fix which has restored Beamery Sandbox, we're continuing to monitor the situation.

Beamery is investigating issues with our Sandbox US tenant relating to a Cloudflare outage following scheduled maintenance.   https://www.cloudflarestatus.com/

All services are operating normally

Cloudflare service causing access issues to Beamery

Cloudflare service outage is continuing to cause intermittent access issues to Beamery services. We are closely monitoring the situation.

All services are operating normally. Some customers based in the US may still experience loading issues on the Beamery application until the third-party fully resolves their issue. We have observed improvements and expect full resolution soon.

We are investigating an increase in errors using Beamery. This is related to the major AWS outage causing a major incident on one of our third-party providers.

All services are operating normally.

Errors are back down and normal operations have resumed

LinkedIn CRM Connect sync is delayed

Across all environments, several modules within Beamery CRM are not functioning as expected, including: • Extension - Generate Email • Candidate Portals • Job Description Generation • Job Description Parsing • Recipes AI Search Beamery Engineering is currently investigating, and further updates will be provided. We thank you for your patience.

All services are operating normally

All affected customers have been contacted with resolution steps and we have confirmed the issue is no longer present for all who have completed the steps.

Some customers are unable to access Beamery via SSO