# Cycles being drained. How to understand what's behind it? **URL:** \ **Category:** Programs & Applications\ **Created:** [November 1, 2022, 8:50am UTC](https://forum.dfinity.org/t/cycles-being-drained-how-to-understand-whats-behind-it/16293 "2022-11-01T08:50:06Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![LightningLad91](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lightninglad91/32/5373_2.png) [@LightningLad91](https://forum.dfinity.org/u/LightningLad91)\ **Post date:** [November 1, 2022, 11:09am UTC](https://forum.dfinity.org/t/cycles-being-drained-how-to-understand-whats-behind-it/16293/6 "2022-11-01T11:09:41Z")
To save you some time: I recommend calling `initCap` if you haven’t already. This will initialize the CAP event service. If you don’t do this your canister will trap when it attempts to report a transaction to CAP. Your canister will catch this error and try again, hundreds of times within a few seconds, and will continue this behavior until you either restart the canister or initialize the CAP service using the command I mentioned in the first sentence. > [@Canister burning through cycles](https://forum.dfinity.org/t/canister-burning-through-cycles/13813/45): > > I apologize for taking so long to follow-up on this thread. We solved the problem a while back and I neglected to close the issue (even after @domwoe was kind enough to remind me). I understand this is not good etiquette on a forum like this. In short, the cycles leak was due to my failure to initialize the Certified Assets Provenance (CAP) service before deploying our NFT canister. During operation, whenever a token was sold or transferred the CAP service would attempt to report that event usi… --- _[View the full topic](https://forum.dfinity.org/t/cycles-being-drained-how-to-understand-whats-behind-it/16293)._