Common problems: integrations

Integration faults rarely announce themselves. A scheduled job reports success, an authentication goes through, an endpoint stays silent, and nothing on screen explains why. This page gathers the symptoms reported most often on the integrations covered in this section, and points to the article that treats each one in full.

I cannot find the screen the documentation describes

Almost every integration depends on an option opened on your account. When the option is not open, the screen is absent rather than greyed out: there is nothing to click, and no message explains the absence.

Ask your Beedeez contact to open the option. Check as well that your own authorisation template carries the configuration rights, because two administrators with different templates do not see the same configuration screens.

The synchronisation reports success but nothing changes

A job that processes an empty file still finishes successfully, so the status alone proves nothing about what was written.

Look at the volume processed rather than the status. Click the run row: the Advanced information window gives the number of lines read, and how many learners were created, updated and deactivated. An empty window means the run did nothing. On the SIRH synchronisation, View files lists what is actually sitting in the drop, which settles the question of whether the file arrived at all. If the counters are low rather than absent, check that the mapping still matches the columns your export delivers. See Monitoring your synchronisations.

Duplicate learners have appeared

The matching identifier changed. Two causes account for most cases: the HRIS export changed the value or the format of the identifier column, or an account was created on the fly from the LMS or from SSO on an identity that does not match the one provisioning uses.

⚠️ Fix the cause before removing the duplicates. Otherwise the next run recreates them. See Identity and provisioning.

SSO signs the learner in as the wrong person

Authentication succeeds and identity matching does not. What the identity provider returns does not correspond to the identifier provisioning uses, so the session opens on another account.

💡 Test with a real account, never one created by hand in Beedeez. A manually created account is precisely the one that carries no HRIS identifier, so it hides this exact fault.

External content displays a blank frame

Some sites refuse to be displayed inside a frame. The refusal comes from the site itself, it produces no error message, and no setting in Beedeez overrides it.

Set the content to open in a New window instead. See Web content.

It works for me and not for my learners

Three differences explain most of these reports. Check them in this order.

1. The network. A workstation in an office is not filtered like a phone connected from a shop, and video platforms are blocked on many corporate networks.
2. The device. A module designed for a desktop screen is often unusable with a finger.
3. The account. You are an administrator and your learners are not. Test with a real learner account, from Signing in as a learner.

My webhook endpoint receives nothing

Check three points in order.

Does an event exist for what you are waiting for? One event reaches endpoints, certificate_completed, sent when a certificate award is recorded. The configuration form offers a second one, certificate_expired, that nothing emits: expiry is sent under the certificate_completed name instead. An endpoint subscribed only to certificate_expired therefore stays silent, with no error and no warning. See Webhook events.

Does your service answer within five seconds? Beedeez waits five seconds for the response, whatever timeout you set on your side, and treats anything else as a failure.

Has the call already failed once? A failed call is not replayed, so the event is lost.

My API integration ran, then stopped after a few hours

The access token expired and renewal is not handled. An access token lives six hours, after which every call is refused until the integration renews it. See Authenticating on the API.

Calendar invitations stopped going out

An authorisation was revoked on the Microsoft or Google side, often when the person who granted it left the company.

⚠️ No alert reaches Beedeez. Sessions keep being created, without invitations. See Syncing sessions with Outlook and Google Calendar.

Beedeez figures and LMS figures do not match

The two platforms do not record the same events at the same moment, so their totals rarely line up exactly. Decide which one is authoritative for your reporting and treat the other as an indicator. See Delivering your Beedeez content to an external LMS.