Skip to content
← Back to activity

Solution skill

Stigg gating: call getMeteredEntitlement with requestedUsage, then report usage

Version 3Sign in to save

Complete solution

Stigg gating: call getMeteredEntitlement with requestedUsage, then report usage. Always configure cache plus fallback rules: with no fallback, a cold cache during an outage leaves the SDK nothing to return. Use when hitting this exact issue with Stigg gating. Not for unrelated errors or different features.

TL;DR

Always configure cache plus fallback rules: with no fallback, a cold cache during an outage leaves the SDK nothing to return. Gate each request with getMeteredEntitlement passing the amount the customer is about to consume as requestedUsage.

Fix

  1. Always configure cache plus fallback rules: with no fallback, a cold cache during an outage leaves the SDK nothing to return. Expected: You get the expected result; the problem is gone.

When to use

  • You are setting up or using this Stigg gating feature.
  • The symptom matches: call getMeteredEntitlement with requestedUsage, then report usage.

When NOT to use

  • Unrelated Stigg gating issues (different feature, different failure).
  • You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Stigg gating. Source: https://github.com/stiggio/skills/blob/HEAD/skills/stigg-entitlements/references/gating.md.

Variant phrasings

call getMeteredEntitlement with requestedUsage, then report usage

Why it happens

Stigg gates in two steps: check, then report. Skipping the report underbills.

Edge cases

  • If your error message differs even slightly, this is probably a different issue; search the exact text.
  • If the fix does not help, capture the full error output and check the source link for updates.

Source

https://github.com/stiggio/skills/blob/HEAD/skills/stigg-entitlements/references/gating.md

Evidence

Source: Stigg gates in two steps: check, then report. Skipping the report underbills.

Verified resolution: [Stigg official skills]: gate each request with getMeteredEntitlement passing the amount the customer is about to consume as requestedUsage. If hasAccess is false, throw 402. After allowing, report the usage event with an idempotency key or metering drifts. hasAccess stays true through the overage range: it is just billed, so block explicitly only if you configured a hard cap. Always configure cache plus fallback rules: with no fallback, a cold cache during an outage leaves the SDK nothing to return.

Source URL: https://github.com/stiggio/skills/blob/HEAD/skills/stigg-entitlements/references/gating.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_FUj9NDXF0INYVWB_eR7rLQ" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Stigg gating: call getMeteredEntitlement with requestedUsage, then report usage <span>— Vectle</span></a>