# Task Not Found Exception(Resolved) **URL:** \ **Category:** Development\ **Created:** [August 23, 2023, 8:16am UTC](https://talk.openmrs.org/t/task-not-found-exception-resolved/40303 "2023-08-23T08:16:29Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![sharif](https://talk.openmrs.org/user_avatar/talk.openmrs.org/sharif/32/11982_2.png) [@sharif](https://talk.openmrs.org/u/sharif)\ **Post date:** [August 23, 2023, 8:16am UTC](https://talk.openmrs.org/t/task-not-found-exception-resolved/40303/1 "2023-08-23T08:16:29Z")
@dkayiwa @ibacher @mozzyI am currently in the process of developing a straightforward ETL (Extract, Transform, Load) query to facilitate the seamless transfer of extracted and transformed data into an OpenMRS database. Regrettably, I’ve encountered a significant obstacle in the form of a task that cannot be located. but when i check in the database, the task name is there, This issue manifests specifically at this point in the codebase: [link to code snippet](https://github.com/openmrs/openmrs-core/blob/73558b0b492b5d1f255844d23658f5d5acb99471/api/src/main/java/org/openmrs/scheduler/db/hibernate/HibernateSchedulerDAO.java#L92C2-L92C71). ---
**Author:** ![sharif](https://talk.openmrs.org/user_avatar/talk.openmrs.org/sharif/32/11982_2.png) [@sharif](https://talk.openmrs.org/u/sharif)\ **Post date:** [August 25, 2023, 7:09am UTC](https://talk.openmrs.org/t/task-not-found-exception-resolved/40303/2 "2023-08-25T07:09:33Z")
Hello, For some reason, the chron job is not able to pick the task defined in manage schedules and hence throw the above exception. Could be a bug in ETL module. ---
**Author:** ![sharif](https://talk.openmrs.org/user_avatar/talk.openmrs.org/sharif/32/11982_2.png) [@sharif](https://talk.openmrs.org/u/sharif)\ **Post date:** [September 4, 2023, 9:54am UTC](https://talk.openmrs.org/t/task-not-found-exception-resolved/40303/3 "2023-09-04T09:54:04Z")
Was able to load data into openmrs patient table. At first the above error log is first thrown but its not neccessary, if and only if some conditions are met. The first condition was to set the OMRS ID to none since we want IDs from outside data merge synchronously with IDS from OMRS.