Error Handling

If the alert is triggered for the oldest unacked message age in batch subscriptions (e.g., event-pers.push.request-publisher.batch.*-sub), this could indicate that message processing is slow or stuck. You can check the subscription status in the Google Cloud Console UI.

Try scaling the workers up or down slightly to see if message processing improves. Usually this resolves the issue if message processing is stuck.

Currently this type of alert for batch processing is under investigation, but since it doesn’t happen frequently, the root cause is not yet confirmed.

If you get a message from one of the results or error workers in the errors topic and you see that it’s not a permanent code-related error (e.g., it was caused by a transient network issue or temporary service outage), you can reprocess the message by publishing it to the event-pers.republisher topic.

Both Results and Errors handler messages (PersonalizationResults format) can be republished. The Republisher will automatically filter out the failed contacts from the failures section, so you do not need to manually edit the message.

The Republisher will create new EventPersMessage messages and publish them back to the Request Publisher Handler for a fresh attempt.