The validator gives no detail on this message, so the most common causes are small mismatches in the exact values the task asks for. Based on the documentation and similar posts from other learners, these are the places to check.
An employee document type combines a topic detail, a security policy and a retention policy. The retention policy pairs a retention period with the HR criteria that decide who it applies to. The HR service can then move case attachments into the repository automatically when a case is closed.
Check each of the following against the task text:
- Confirm the document type name is exactly Travel Advance Requests, with Topic Detail set to Payroll System and Employee access checked. Copy and paste the names to rule out stray spaces.
- On the new retention policy, confirm the HR criteria is FTEs with 1 year or more and the retention period is Case Created + 1 year. If either record was created under a slightly different name, create it again with the exact wording.
- Open the Travel Advance Request HR service and check that Automatically move attachments is ticked. If the Employee document type field is not on the form, configure the form layout to add it, because a community answer notes it only shows when the checkbox is ticked.
- Set Employee document type on the service to Travel Advance Requests.
- Make sure the Topic Detail on the HR service matches the Topic Detail on the document type. A community answer to a learner whose document type list was empty names this as the cause.
- Check that you are working as the role the lab expects. Retention policy changes need the sn_hr_ef.manager role, and some lab tasks require impersonating a specific user.
- In the Employee Document Management lab environment, a community answer suggests setting the cross-scope access records that involve the Employee Document Management scope to Allowed, if you see cross-scope errors.
If everything matches and it still fails, run the Debug simulator task option for the failed task. A community answer says it gives a detailed analysis of what the validator found. You can also terminate the instance and request a fresh lab instance, then redo the task. Your screen shows one extension and two instances remaining, so there is room to retry. Finally, a community answer says a lab can be completed at 80 percent progress, so one failed task need not block you unless a later task depends on it.
Sources:
