Lifecycle Import Automation | XM Community
Skip to main content

After turning on the participant import automation for 2 lifecycle projects last week, there are still no participants being loaded into the project. 

 

I have tried matching the criteria with the directory and ensured that it should be pulling results and the scheduled invitations are “sending” but to no participants because no one is loaded into the project.

 

Has anyone else run into this issue or have any suggestions for things to check?

Been disappointed we haven’t reached a resolution sooner, so hoping someone can help!

Hey @zEmma,

seems like you need to check the import automation setup further. 

  1. Metadata Conditions: Ensure that the metadata conditions you've set for the automation match the metadata in your Employee Directory. The conditions are case-sensitive and must match exactly.

  2. Automation Schedule: Check the schedule you've set for the automation. The automation will only run at the specified times.

  3. Automation Status: Make sure the automation is enabled. If it's turned off, it won't run even if the schedule and conditions are set correctly.

  4. Errors in Import: Check for any error messages that might have appeared after importing participants. These messages can provide clues about what went wrong.

  5. Participant Import Conditions: Ensure that the conditions you've set for importing participants are correct. For example, if you're using date fields, make sure the conditions are set correctly for the number of days before or after today.

Best
Christian

Hey @zEmma,

seems like you need to check the import automation setup further. 

  1. Metadata Conditions: Ensure that the metadata conditions you've set for the automation match the metadata in your Employee Directory. The conditions are case-sensitive and must match exactly.

  2. Automation Schedule: Check the schedule you've set for the automation. The automation will only run at the specified times.

  3. Automation Status: Make sure the automation is enabled. If it's turned off, it won't run even if the schedule and conditions are set correctly.

  4. Errors in Import: Check for any error messages that might have appeared after importing participants. These messages can provide clues about what went wrong.

  5. Participant Import Conditions: Ensure that the conditions you've set for importing participants are correct. For example, if you're using date fields, make sure the conditions are set correctly for the number of days before or after today.

Best
Christian

@chackbusch thank you for the response. 

 

  1. All conditions match and results populate when replicating the conditions within the Directory search.
  2. The automation is set to run every night.
  3. The automation is turned on and has been for over a week, but there are still no participants within the project.
  4. There are date criteria being used. Would you agree with this setup?
    1. To target pulling in employees when they reach 30 days since their hire date it is set as:
      1. 29 days before today
      2. 31 days before today

Hey @zEmma, 

could you please add a screenshot of the filter setup? 

Best
Christian

@chackbusch This is the setup to have the import pull in participants on their 30th day since their hire date. 

 

@chackbusch Please ignore the screenshot above. I have solved my initial issue. But I wanted to ask another question about the dates if you have any insight. 

For another lifecycle project we would like participants to be picked up “the next day”, so what would that language need to look like for the “days before today”/”days after today” conditions? You can imagine the same as in the screenshot above, but the goal would be 1 day instead of 30. 

Leave a Reply


Terms & Conditions