Prepare grouping fields for group-scoped rules

​

Summary

In self-hosted deployments, group-scoped automation rules do not run if the project-level grouping field is not provisioned. Creating or updating a group rule through the API does not automatically prepare a new grouping field. Open the rule in the UI and click Update automation to prepare the field so grouped scoring runs.

​

What is happening

When a group-scoped rule is created or updated through the API, a new project-level grouping field is not automatically prepared. The grouped-scoring worker fails before calling the scorer because the database lookup index and metric columnstore entry are missing. The worker retries silently. Span-scoped and trace-scoped rules are unaffected.

​

Fix or suggestion

​

UI reprovision

1. Go to Settings > Automations in the target project.
2. Open the group-scoped rule that groups on the field you use.
3. Make a small change, for example, edit the description.
4. Click Update automation.
5. Wait for indexing and backfill to finish, then send a fresh test thread.

This UI save prepares the lookup index, enables the metric columnstore for the field, and starts the required backfill. Save one group rule in the UI for each project and grouping field. Other rules using that field in the same project share the preparation. Adding the field under Subfield indexing on Settings > Query optimization does not replace the UI provisioning.

​

How to confirm it worked

• In the rule’s Automation configuration, confirm that Group by shows the intended field.
• Check Processing status for pending segments or errors, then verify that a fresh matching thread is scored.
• Verify new automation spans appear and that spans include the metadata.grouped_scoring marker.

​

Notes

• Existing failed work can take up to one hour to retry after provisioning.
• This behavior is a known limitation. API-created group rules do not provision the grouping field or surface an error when the index is missing.