# Commit confirmed with timeout rollback, is not able to revert data from CDB **URL:** \ **Category:** NETCONF\ **Created:** [August 18, 2016, 1:17pm UTC](https://dmap-community.ductus.global/t/commit-confirmed-with-timeout-rollback-is-not-able-to-revert-data-from-cdb/637 "2016-08-18T13:17:53Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![sachin.mahajan](https://avatars.discourse-cdn.com/v4/letter/s/e9bcb4/32.png) [@sachin.mahajan](https://dmap-community.ductus.global/u/sachin.mahajan)\ **Post date:** [August 18, 2016, 1:17pm UTC](https://dmap-community.ductus.global/t/commit-confirmed-with-timeout-rollback-is-not-able-to-revert-data-from-cdb/637/1 "2016-08-18T13:17:53Z")
I tried configure the data using NETCONF followed by commit confirmed with some persist-id and timeout of 40 secs. After timeout is over, i got message showing configuration is reverted. But actually configured data is present in CDB, it is not reverted. This i ran with candidate database. Your help is appreciated, thanks in advance. ---
**Author:** ![cohult](https://yyz2.discourse-cdn.com/flex010/user_avatar/dmap-community.ductus.global/cohult/32/221_2.png) [@cohult](https://dmap-community.ductus.global/u/cohult)\ **Post date:** [August 18, 2016, 2:15pm UTC](https://dmap-community.ductus.global/t/commit-confirmed-with-timeout-rollback-is-not-able-to-revert-data-from-cdb/637/2 "2016-08-18T14:15:45Z")
Hi, Make sure that you read from the CDB running datastore and not from the CDB candidate datastore when you check if the configured data is present in CDB. When you commit confirmed the configuration, the candidate datastore diff vs running it is written in a transaction to the running datastore. If the commit is not confirmed the configuration in the running datastore is reverted, but the configuration still remain in the candidate datastore.