HERO Usage Limits and Troubleshooting
How the weekly meter works The usage meter reflects the property's shared HERO chat spend for the current property-local week. The window resets Monday at 8:00 a.m. in the property's timezone. Below...
Last updated
How the weekly meter works
The usage meter reflects the property's shared HERO chat spend for the current property-local week. The window resets Monday at 8:00 a.m. in the property's timezone.
- Below the limit, the meter shows the percentage used.
- Near the limit, HERO warns that the allowance is almost used.
- At the limit, new model-backed HERO requests stop until the displayed reset time. Existing records and the rest of URBI remain available.
- Arthur voice, SMS, email, and in-app conversations do not use this HERO allowance and continue operating.
HERO is hidden on subscription tiers that do not include it. If the entry point is missing, confirm the property's subscription before troubleshooting the weekly meter.
The percentage is rounded down for display, so a property is not shown as fully stopped before it actually reaches the limit.
A card says “Still running”
HERO stopped polling before the background action reached a final status. Do not submit a duplicate action. Leave the conversation open or return to it; the card updates from the saved status when the action completes or fails.
An action failed
Read the reason on the card. Choose Edit to correct its fields, or Retry to submit a new attempt. In an approved plan, later actions remain pending after the first failure.
An access request reports a conflict
The selected unit already has one or more overlapping open access requests. Adjust the access window or audience, or reject the proposal. The warning appears before acceptance and does not create an access request by itself.
A full-list export does not start
Confirm that the result came from an accepted HERO query, you still have access to the property, and the result is below 50,000 rows. If the problem continues, send support the property ID, conversation ID, and the approximate time of the attempt.
HERO asks me to sign in again
Your session expired before approval. Sign in, return to the conversation, and approve the still-pending action again. HERO does not dispatch the action when session verification fails.