A candidate can be created via API with a job posting that is not a part of the job feed. This could be because:

• The job feed has not yet been refreshed, so our master feed does not have the proper requisition to create the candidate against.
• The job is no longer externally posted and is not part of the job feed, but recruiters are still recruiting candidates for the role.

If one or both of these scenarios can apply to your client at any time, then you can assign those potential candidates the Default Journey Targeting flow in order to ensure that they have a path to follow through the hiring process instead of falling into a “black hole” where we do not know what conversation, form, scheduling request, etc. to send them.

To enable this functionality, complete the following steps.

1. Select the All Apps menu in the top left corner of the header and then Settings in its drop-down menu.
2. When the Settings page opens, select Job Manager under the Jobs section.
3. The Job Manager will open to the Journey Targeting section. Open the Default Journey Targeting flow.
4. Select the # requisitions targeted button in the right corner above the Set Targeting box.
5. When the targeted requisitions modal opens, select the settings icon to the right of the search bar and toggle on Accept Candidates with Unknown Job Data. 
6. Select Done.
7. Select Next Step in the top right corner of the section.
8. Select Save and Publish in the top right corner of the section.

After this is enabled, you can easily disable this functionality as needed by repeating the process but toggling off the Accept Candidates with No Job Data toggle.