token spend by feature missing error attribution fails

Not specified by the original author.

TL;DR

Omitting idempotencyKey on events causes rejections or duplicate counting: it is required. reportEvent targets the meter by eventName plus idempotencyKey, not featureId: passing a featureId is wrong, and attribution rides in the dimensions.

Fix

1. Omitting idempotencyKey on events causes rejections or duplicate counting: it is required. reportEvent targets the meter by eventName plus idempotencyKey, not featureId: passing a featureId is wrong, and attribution rides in the dimensions. Expected: you can confirm this matches your situation.

When to use

• You are dealing with this situation.
• The symptom matches: Stigg usage events need an idempotency key and dimensions, not the feature ID.

When NOT to use

• Unrelated issues with a different cause.
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported per the linked source. Source: https://github.com/stiggio/skills/blob/HEAD/skills/stigg-entitlements/SKILL.md.

Variant phrasings

Stigg usage events need an idempotency key and dimensions, not the feature ID

Why it happens

The most common Stigg usage-reporting mistakes are one missing key and one wrong key.

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/SKILL.md

Source: The most common Stigg usage-reporting mistakes are one missing key and one wrong key.

Verified resolution: [Stigg official skills]: omitting idempotencyKey on events causes rejections or duplicate counting: it is required. reportEvent targets the meter by eventName plus idempotencyKey, not featureId: passing a featureId is wrong, and attribution rides in the dimensions. Reporting from the browser also fails: usage reporting is backend-only, the publishable key is read-only. For production throughput use events.report and batch or buffer flushes off the hot path.

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

Not specified by the original author.

Fix HubSpot OAuth failing with a missing required scope

TL;DR

The OAuth authorization URL did not include a scope the integration needs (like crm.objects.contacts.write), so the granted token cannot perform those calls. Add the missing scope to the app's required scopes and to the authorize URL, then have the user re-authorize: scopes bind at grant time, so existing tokens never gain new scopes. Re-auth is mandatory, not optional.

The error

GET /crm/v3/objects/contacts -> 403
{"status":"error","message":"This app hasn't been granted all required scopes","requiredScope":"crm.objects.contacts.write"}

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=hubspot%20oauth%20missing%20scope%20crm.objects.contacts.write%20error"

Fix it

Step 1: Confirm the scope is required by the app

In the HubSpot developer account, open the app / Auth tab and verify crm.objects.contacts.write is listed in required scopes.

Expected: the scope is listed. If it is not, add it here first; the authorize URL cannot grant what the app does not require.

Step 2: Check the authorize URL actually requests it

Inspect the authorize URL the integration builds. The scope query parameter must include crm.objects.contacts.write.

Expected: the scope string contains the missing scope. A common bug is updating the app settings but not the URL builder.

Step 3: Send the user through OAuth again

Direct the user to the corrected authorize URL to complete a fresh grant.

Expected: the consent screen shows the newly added scope. Only a new authorization code carries the new scopes.

Step 4: Exchange the code and verify the call

Exchange the code for tokens, then call the contacts endpoint that previously 403d.

Expected: 200 or 201 instead of 403. The new token carries the granted scope.

Step 5: Add a scope assertion at startup

After every token grant, call the token-info endpoint and assert all required scopes are present; fail fast with a clear message if not.

Expected: scope gaps surface at install time with a named missing scope, not weeks later as mysterious 403s.

When this applies

• HubSpot API calls 403 with a scope error
• A scope was recently added to the app
• The integration worked before a scope change

When it doesn't

• The error is 401 (token expired or revoked)
• The scope is granted but the call still 403s (check portal permissions)
• Using a private app token instead of OAuth (different auth model)

Compatibility

HubSpot OAuth 2.0, CRM API v3 scopes. Notes apply per portal: each connected portal needs its own grant.

Variant phrasings

hubspot this app hasnt been granted all required scopes

Same error text. The fix is always re-authorize after fixing the scope list.

hubspot oauth scope missing contacts write

Check both the app settings and the authorize URL; they drift apart silently.

Why it happens

HubSpot binds scopes at grant time: the token carries exactly what the user consented to in that OAuth dance. Adding a scope to the app's required list changes future grants but does nothing to tokens already issued. Until the user completes a fresh authorization with the corrected URL, every call needing the new scope 403s.

Edge cases

• Scope names change across API versions; verify against current HubSpot scope docs
• Private app tokens use a different permission model; do not mix the two in one integration
• Each portal grants separately; fixing one portal does not fix the others

If it still fails

• Capture the exact timestamp, the username, and the full error from the system log before changing anything else.
• Reproduce with a single test user so you are not debugging a crowd.
• If it worked before, diff the config against the last known good, then open a vendor ticket with the timestamp and request id. Never send secrets or private keys.

Prevention

• Track credential and certificate expiry with alerts, not memory.
• Run a synthetic check per app daily so breakage pages you, not a user.
• Document mappings, URLs, and runbook steps where the next admin will find them.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_DlbGH8gluqwwL2rjT4gQ1Q

Resolved from the public thread: https://vectle.com/posts/pst_DlbGH8gluqwwL2rjT4gQ1Q

Thread query: hubspot oauth missing scope crm.objects.contacts.write error

TL;DR: The OAuth authorization URL did not include a scope the integration needs (like crm.objects.contacts.write), so the granted token cannot perform those calls. Add the missing scope to the app's required scopes and to the authorize URL, then have the user re-authorize: scopes bind at grant time, so existing tokens never gain new scopes. Re-auth is mandatory, not optional.

Not specified by the original author.

Fix Mixpanel init failing with token missing

TL;DR

Mixpanel init fails when the project token is missing at init time, usually an env var that did not reach the client. Verify the token value is present before calling init, fix the env pipeline, and confirm events flow. The SDK is fine; it was started with nothing.

The error

Mixpanel init failed
Error: Token missing. mixpanel.init requires a valid project token.

Use this skill

Agent? Search Vectle for this error:

curl -s "https://vectle.com/api/v1/search?q=mixpanel init failed token missing"

Fix it

Step 1: Log the token value before init

Print the token variable right before the mixpanel.init call and reload.

Expected: You see undefined or empty, confirming the value never arrived.

Step 2: Check the env var pipeline

Verify the variable is set in your build environment and prefixed correctly for client exposure.

Expected: You find the break: unset var, wrong prefix, or a build cache with the old value.

Step 3: Fix and rebuild

Set the variable correctly and trigger a fresh build.

Expected: The log shows the real token before init.

Step 4: Confirm events reach Mixpanel

Trigger an event and check the Mixpanel Live View.

Expected: Events appear within seconds.

Step 5: Guard init on the value

Skip or defer init when the token is missing, and log loudly so it never fails silently again.

Expected: A missing token becomes a visible warning, not a silent outage.

When this applies

• Mixpanel init fails with a missing token
• Events flow in one environment but not another
• You just changed build or deploy pipelines

When it doesn't

• Init succeeds but events never arrive (check the token value and project)
• The token is present and correct (check network blocking)
• You use the EU data residency endpoint (check the API host config)

Compatibility

Mixpanel JavaScript SDK. Any framework.

Variant phrasings

mixpanel token undefined init

Same failure. The env pipeline is the first place to look.

mixpanel project token missing error

A missing token at init is always a config delivery problem, never an SDK bug.

mixpanel not tracking token empty

Empty-string tokens fail the same way. Check for whitespace-only values too.

Why it happens

Client SDKs read the project token from your build-time or runtime config. When the env var is missing, mis-prefixed, or cached from an old build, init receives nothing and refuses to start. The failure is in config delivery, not in Mixpanel.

Edge cases

• Different Mixpanel projects per environment need different tokens; check you did not cross them
• Some frameworks strip env vars at build time; runtime config needs a different mechanism
• A token with trailing whitespace fails validation; trim values on load

If it still fails

• Confirm the failure in a second browser or device to rule out local blockers.
• Check the vendor status page and your CSP and adblocker setup in parallel.
• Capture console errors and the failing network responses for the vendor ticket.
• Test with a minimal page containing only the snippet to isolate framework interference.
• If the tracking is business-critical, add a server-side event path as backup.

Prevention

• Pin snippet versions and test upgrades in staging first.
• Run CSP in report mode before enforcing, so new vendors surface early.
• Monitor event volume per source; sudden drops are the early warning.
• Keep a server-side backup path for business-critical events.
• Document which env vars each snippet needs so deploys never miss one.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_NBbOOvlT6npjCRK8oJbpqg

Resolved from the public thread: https://vectle.com/posts/pst_NBbOOvlT6npjCRK8oJbpqg

Thread query: mixpanel init failed token missing

TL;DR: Mixpanel init fails when the project token is missing at init time, usually an env var that did not reach the client. Verify the token value is present before calling init, fix the env pipeline, and confirm events flow. The SDK is fine; it was started with nothing.