Skip to main content
Question

Issue with our HRIS info updating

  • May 4, 2026
  • 2 replies
  • 40 views
kprim
Novice I

I am posting  for my tech person who is building out our recipes. We would appreciate any help possible. 


"We have a batch recipe (modeled off the Azure example) that is not picking up changes to users, but when I run the recipes one-off for just that user they pick up just fine. Our recipes are linked to Snowflake, and run 2x daily after snowflake updates. Example: I made an update to 2 user profiles, made sure their new data was in snowflake, and ran the batch. It did not pick up the users. I then used a WHERE SQL filter on the snowflake trigger in the same recipe for just 1 user at a time, and it worked. the recipe picked them up and created them in Docebo with all the correct information. Why were these users not picked up in my batches? There are 3 batches each recipe run, and each batch has different users."

2 replies

hailey.gebhart
Helper III
Forum|alt.badge.img

Hi there,

 

We would need more details on the specifics of your recipe. Docebo Connect (AKA Workato) works based off of data pills. If your recipe schemas and samples are not exactly what you are outputting from your batches, it will miss the items. Usually if you have some sort of loop or batch, and you are only receiving one item, that means the recipe is not iterating through the users properly.

 

Do you have any additional details on how you set up the recipe, how you are getting the information, and how the data is being handled?

    kprim
    Novice I
    • kprim
    • Author
    • Novice I
    • May 4, 2026

    ​@hailey.gebhart  Thank you for your response. 

    The recipe is using the Create/Update users in Snowflake [batch]. All field names are exactly as they are in the output. The Create/Update part of the job does in fact pull all users, but when it gets to the batch processes it only shows one person. I was told by support this is normal, it only displays the last person in the batch. Are you saying that's not correct?

    Terms & ConditionsAccessibility statement