Crash/error reporting delivers warnings to our technical team when Daycast encounters a difficulty. These warnings may be user-specific, but they are not about what you do inside the app; they’re about how the app itself is performing. Users who have crash/error reporting enabled allow us to solve certain problems before the issue can impact them—think of it as ‘precog’ for bug reports. For example, a bug in version 1.0.0 caused time submission failures for tasks that were both A) forwarded from a previous day and B) linked to a FreshBooks project via integration. Crash/error reports alerted our developers to the problem, allowing them to correct the time submission failures as they occurred and deploy a permanent bug fix in version 1.0.1. As a result, Daycast users were not affected by the problem.