# Job automatic retry on failure **URL:** \ **Category:** Uncategorized\ **Created:** [June 14, 2022, 12:36pm UTC](https://community.dremio.com/t/job-automatic-retry-on-failure/9282 "2022-06-14T12:36:47Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![allCag](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@allCag](https://community.dremio.com/u/allCag)\ **Post date:** [June 14, 2022, 12:36pm UTC](https://community.dremio.com/t/job-automatic-retry-on-failure/9282/1 "2022-06-14T12:36:47Z")
Hello, we have been experiencing a few job (reflection or query) failures due to external reasons (Eg. error Remote backend is unreachable (502 Bad Gateway)). The problem in such cases is that the job, such as a long running reflection, is not retried automatically. Note: Physical datasets set to “Never Refresh” and “Never expire” and launch of PDS dependent reflections done using the API catalog refresh functionality. Is there a “retry” functionality in Dremio in case of such job failures ? Rgs, Alexandre ---
**Author:** ![Benny\_Chow](https://sea2.discourse-cdn.com/flex020/user_avatar/community.dremio.com/benny_chow/32/5527_2.png) [@Benny\_Chow](https://community.dremio.com/u/Benny_Chow)\ **Post date:** [June 16, 2022, 6:33pm UTC](https://community.dremio.com/t/job-automatic-retry-on-failure/9282/2 "2022-06-16T18:33:51Z")
Unfortunately, there is no retry in this case. There’s another outstanding issue where if you query this reflection from the sys.reflections table, it’ll have a status of CANNOT\_ACCELERATE\_SCHEDULED. This would make a good improvement since Dremio does retry reflections whose physical dataset have refresh periods configured. ---
**Author:** ![allCag](https://avatars.discourse-cdn.com/v4/letter/a/ac91a4/32.png) [@allCag](https://community.dremio.com/u/allCag)\ **Post date:** [June 20, 2022, 12:06pm UTC](https://community.dremio.com/t/job-automatic-retry-on-failure/9282/3 "2022-06-20T12:06:47Z")
Tks for your feedback @Benny_Chow