Skip to main content
Integrations

Support Connect Check-Up Guide

  • December 8, 2025
  • 0 replies
  • 49 views

Laura AD
Docebian

This Docebo Connect Check-Up List provides a clear, step-by-step methodology to effectively retrieve and review essential configuration details of their Connect recipes. The primary goal is to streamline the troubleshooting process by ensuring all critical settings are accurately documented and verified.

 

 

How to know if Connect Recipes are active?

  1. Navigate to the Admin menu> Docebo Connect >Manage 
  2. On the right side menu, select “Recipes
  3. In the Recipe, a green chip “Active” appears if the recipe is active

 

 

How to know if customizations have been applied to the recipe?

  1. Navigate to the Admin menu> Docebo Connect >Manage 
  2. Select the recipe to be examined in one window
  3. Duplicate this window and select the original example recipe
  4. Compare them

 

 

Have you made recent modifications to the recipe?

  1. Navigate to the Admin menu> Docebo Connect >Manage 
  2. Select the recipe to be examined
  3. Click the "Settings" tab in the upper menu
  4. Locate the "Activity Audit" option and click the hyperlink to access the "Audit Log"
  5. View recent actions and changes in the "Audit Log"

 

 

Are duplicated jobs for the same recipe?

  1. Navigate to the Admin menu> Docebo Connect >Manage 
  2. Select the Dashboard tab
  3. Check Recent Jobs and search for duplicates

 

 

Have the templates been updated to the latest version?

  1. Navigate to the Admin menu> Docebo Connect >Manage 
  2. Select the recipe to be examined
  3. Click the "Settings" tab in the upper menu
  4. Locate the "Copied From" option
  5. If an alert message about a new template version appears, it means the update has not yet occurred.

 

 

Are there active webhooks, and do they have any errors?​​​​​​​

  1. Navigate to the Admin menu> Docebo Connect >Manage 
  2. Validate the webhooks in the selected recipe
  3. Navigate to the Admin menu> Webhooks >Manage 
  4. Locate the relevant webhook
  5. If an error is present, retrieve it