# Cron jobs on ICP

**URL:** <https://forum.dfinity.org/t/cron-jobs-on-icp/1403>\
**Category:** Developers\
**Created:** [October 10, 2020, 8:06pm UTC](https://forum.dfinity.org/t/cron-jobs-on-icp/1403 "2020-10-10T20:06:12Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![Samer](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/samer/32/8943_2.png) [@Samer](https://forum.dfinity.org/u/Samer)\
**Post date:** [April 30, 2024, 7:38pm UTC](https://forum.dfinity.org/t/cron-jobs-on-icp/1403/21 "2024-04-30T19:38:15Z")

</div>

Note, there currently no way to know if the function triggered by a timer trapped during execution, unless you store some kind of log message at the end of the function.

Soon there will be canister logs that help with this 🙂

---

<div class="post-metadata">

**Author:** ![Samer](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/samer/32/8943_2.png) [@Samer](https://forum.dfinity.org/u/Samer)\
**Post date:** [April 30, 2024, 8:30pm UTC](https://forum.dfinity.org/t/cron-jobs-on-icp/1403/22 "2024-04-30T20:30:07Z")

</div>

> [@Canister Logging Support \[Community Consideration\]](https://forum.dfinity.org/t/canister-logging-support-community-consideration/25571):
>
> Background When a canister traps, changes it makes to the state are completely reverted. As a result, it’s not possible for developers to detect these errors. The IC provides a way to log messages throughout execution, the debug\_print API, but it’s only available when running the canister locally. Problem There is no reliable way for canister developers to know that their canister is trapping. Traps leave no trace in the replica that’s visible for developers. debug\_print is available locally…

[Previous page](https://forum.dfinity.org/t/cron-jobs-on-icp/1403.md?page=1)
