If a featured app team accidentally fires an incorrect marker, what protocols do they need to follow in order to resolve it?

If a featured app team accidentally fires an incorrect marker, what protocols do they need to follow in order to resolve it?

There are two distinct scenarios here:

1. If the team fired significantly more activity markers than their actual network traffic justifies:
The right path is to proactively reach out to the Canton team, report the incident, explain what caused it and what measures have been put in place to prevent it from happening again. The team should also express willingness to return any incorrectly received rewards. Transparency here is key — Canton Foundation will appreciate teams that self-report rather than stay silent.

2. If the activity marker was attached to the wrong transaction (but volumes are correct):
A one-time misfire on an individual transaction is not a critical issue. The simplest way to correct it is to offset it going forward — skip the marker on the transaction that should have been marked originally. No formal escalation needed for isolated cases.

One broader point worth noting: activity marker-based rewards are expected to transition to a traffic-based model in the near future. Regardless of the mechanism, Featured Apps are expected to perform a clear and verifiable function on the Canton Network — that standard remains constant across both systems.