OrderAssessmentCreate GraphQL mutation facts hard limit?

GraphQL Admin API Troubleshooting
1

Dear Community and Shopify Developers!

My team hit a facts limit of 20 on the `orderAssessmentCreate` mutation on the graphql API.

As per the documentation ( orderRiskAssessmentCreate - GraphQL Admin ) there is no hard limit documented at the moment, but seems to me, that 20 is a hard limit.

Could you clarify what are the limitations of this API regarding facts? Somebody could share any previous experience? The Rest documentation didnt help me either: Order Risk

Is this applicable for every store? or does this limitation differ between subscription plans?

Thanks for your answers in advance!
Happy Coding,
Bendeguz Gulyas

2

Hey @Bendeguz_Gulyas1, I was able to confirm this and 20 is a hard limit on the facts field in orderRiskAssessmentCreate, and it applies to every store regardless of subscription plan.

I reproduced it on a dev shop using API 2026-04: 20 facts succeeds, 21 returns a user error with code TOO_MANY_FACTS and the message “The assessment cannot have more than 20 facts.”

The specific limit isn’t called out on the mutation page itself or on the OrderRiskAssessment object page in our docs, so we will look at updating that.

One thing to be aware of is the 20-fact limit is per assessment, per app, per order, so it doesn’t accumulate across multiple submissions. When you resubmit an assessment for an order, it replaces your app’s previous one rather than adding to it. Each app also maintains its own assessment independently, so the 20-fact limit applies separately to each app working on the same order.

Let me know if you’re running into a use case where 20 facts isn’t enough as that would be helpful context to pass along to our product teams..

4

Thanks for the clear explanation of the functionality! And for updating the docs!

I would consider this an edge case, instead of a use case in our situation.

Personally, I think 20 should be granular enough / assessment, to decide, if this evaluation is to the merchants liking or not. I would also think that this amount of fact info, could contain unnecessary noise as well. But if I’m able to fetch more use case context, im going to share it, for sure :slight_smile:

Thanks again!
Happy Coding!
Bendeguz Gulyas