`Import` a space throws `Rate limit error`
See original GitHub issueImport
a space is not working
Actual Behavior
When I run
contentful space import --space-id <id> --content-file contentful-export.json --content-model-only --skip-locales --skip-content-publishing
I always get the same error
13:20:73 - Rate limit error occurred. Waiting for 1568 ms before retrying...
Steps to Reproduce
export
a space into a fileimport
the exported space into a newly created space
Environment
- Node: v8.10.0
- npm 5.6.0
- OS: macOS 10.13.4
Screenshot
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Severe rate limiting when running the python example
Hello Cameron, The RATE_EXCEEDED error usually occurs when too many requests were made to the API in a short period of time. The...
Read more >Understanding and implementing rate limiting in Node.js
Once the user exceeds that number, we can ignore the request and throw an error indicating that the user has exceeded their limit....
Read more >Resolve errors | Google Drive
This error appears when the application's owner has set a quota limit to cap usage of a particular resource. To fix this error,...
Read more >Error java.lang.OutOfMemoryError: GC overhead limit exceeded
This message means that for some reason the garbage collector is taking an excessive amount of time (by default 98% of all CPU...
Read more >Troubleshoot Dataflow errors | Google Cloud
This error occurs if your job's graph size exceeds 10 MB. Certain conditions in your pipeline can cause the job graph to exceed...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Figured out it was just a warning and not an error 🙈 That said, the success message should be listed after the warnings.
Got error
VersionMismatch: Status: 409 - Conflict
while importing Tags. Any reasons why it might happen? At the same time some of tags imported without errors, some with errorVersionMismatch
, couldn’t find correlation 😦