feat(ui): surface content-api usage limit errors#17389
Open
JessRynkar wants to merge 2 commits into
Open
Conversation
Contributor
📦 esbuild Bundle Analysis for payloadThis analysis was generated by esbuild-bundle-analyzer. 🤖
Largest pathsThese visualization shows top 20 largest paths in the bundle.Meta file: packages/next/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_index.json, Out file: esbuild/index.js
Meta file: packages/payload/meta_shared.json, Out file: esbuild/exports/shared.js
Meta file: packages/richtext-lexical/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_client.json, Out file: esbuild/exports/client_optimized/index.js
Meta file: packages/ui/meta_shared.json, Out file: esbuild/exports/shared_optimized/index.js
DetailsNext to the size is how much the size has increased or decreased compared with the base branch of this PR.
|
JessRynkar
marked this pull request as ready for review
July 20, 2026 09:21
JessRynkar
requested review from
AlessioGr,
JarrodMFlesch and
jacobsfletch
as code owners
July 20, 2026 09:21
JessRynkar
commented
Jul 20, 2026
|
|
||
| return { formState: contextRef.current.fields, res } | ||
| } catch (err) { | ||
| console.error('Error submitting form', err) // eslint-disable-line no-console |
Member
Author
There was a problem hiding this comment.
not removed, just moved to line 564 after throwing the usage limit error
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What
Surfaces the following new FC usage limit errors:
cloud_limit.cms_assets_bytes_exceededwhen upload size is exceededcloud_limit.document_count_exceededwhen total allowed document count is reachedcloud_limit.per_document_data_bytes_exceededwhen maximum document JSON size is reachedDesign here.
IMPORTANT:
I tested this by throwing dummy errors that replicate the error code and status.
Currently when testing against the actual
content-api, the error messages are getting masked into a generic 500 status error. This seems to be happening infigma/payload/payload-plugin/src/db-content-apiwhere we catch and re-throw any error as:Once this is resolved, we need to revalidate that this works end to end.
UI Preview
https://github.com/user-attachments/assets/5c5785de-c2f2-4705-b065-5532a43f94a4