fix: two important usage billing fixes #460
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
use a CID as an idempotency key - some Stripe usage billing reporting requests were failing because the space DID was much longer than we expected and the idempotency key cannot be more than 255 characters - we were sending ~450 characters in many cases
properly configure the "on failure" queue for the usage table handler - the previous config didn't work, and no "on failure" destination was set for this, which is, I suspect, why we can't find any trace of some usage table insert hook invocations