Cycles being drained. How to understand what's behind it?

[LightningLad91]

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

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…