When my worker runs out of CPU time, it generates hundreds of errors

When my worker runs out of CPU time, it generates hundreds to thousands of errors that just say that the worker has exceeded its CPU time limit. This is creating a bunch of observability events that I'd rather not pay for, so I'm looking for a way to make sure only one event is being created when this happens.