You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Proposal
We have a ton of users that try to backfill a materialization rather than a capture. This works fine if they have storage mappings but doesn't work well if they don't have them and their collection is more than 20 days old.
It would be nice if we could pop up a warning message in two scenarios:
They backfill a collection that's over 20 days old which uses our trial bucket.
"Your account uses Estuary's Trial bucket which includes 20 days of storage and this collection is older than that. Data will be missing if you backfill from the materialization so we recommend backfilling from the source."
They add a collection that is over 20 days old to a materialization.
"Your account uses Estuary's Trial bucket which includes 20 days of storage and this collection is older than that. To ensure you have all data, please also backfill this collection from the source after adding it to the materialization."
The text was updated successfully, but these errors were encountered:
This should be aggressive and the user should need to dismiss this to continue doing what they are doing. This REALLY causes issues and needs to be made clear to the user.
Is it possible to link to the capture that we're suggesting they backfill as part of the message?
I would also recommend including a link to information + instructions about storage mapping and configuring their own
Proposal
We have a ton of users that try to backfill a materialization rather than a capture. This works fine if they have storage mappings but doesn't work well if they don't have them and their collection is more than 20 days old.
It would be nice if we could pop up a warning message in two scenarios:
The text was updated successfully, but these errors were encountered: