This topic was automatically generated from Slack. You can find the original thread here.
Good morning. Came in today and noticed many of our workflows have been throwing the following errors:
Error communicating with data store
at null.createError (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/core/createError.js:16:15)
at null.settle (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/var/task/node_modules/@lambda-v2/component-runtime/node_modules/axios/lib/adapters/http.js:269:11)
at IncomingMessage.emit (node:events:529:35)
at null.endReadableNT (node:internal/streams/readable:1368:12)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Can anyone one point me in the right direction. The affected workflows haven’t changed recently and have been humming along for months (some even years)!
Hi , I looked into your account and this is happening because your workspace is over the data store quota. You can check the limits on the usage dashboard at the bottom left. Also, see our docs here.
While your workspace is above limits, your data stores are kept on read-only mode. Here’s our guide on exporting the data to an external service. After that, you should delete extra data stores and data to get under the limits: Data Stores - Pipedream
we’ve been sending period emails to users over limits prior to enforcing them.
The first notice email we sent was on December 4th, 2023 and we started enforcing the limits on April 1st, 2024.
I’m going back through old email (I don’t delete things, just archive) and we have received no notification about this change.