...
| Expand | ||
|---|---|---|
| ||
Some accounts may have a fixed time for refresh tokens, such as Google accounts, which must be refreshed every hour. If that refresh needs to occur when the platform is down for an update, the refresh does not occur. To prevent these accounts from failing after a new platform deployment, it is recommended that you refresh your accounts before the designated down time. |
Org Environments
| Expand | ||
|---|---|---|
| ||
User separate Orgs for production, development, and testing activities. Do not use the same Org for the following activities:
|
| Expand | ||
|---|---|---|
| ||
Every quarterly release is available a week early on UAT. Only use UAT for testing release features during the two-week window of the release. We do not recommend ongoing tests or experiments on UAT because the version might change suddenly outside of the two-week window. |
| Expand | ||
|---|---|---|
| ||
Use a Cloud storage provider to store production data. File Assets should not be used as a file source or a destination in production pipelines. When you configure File Reader and Writer Snaps, set the file path to a cloud provider or external file system. Only use
|
Pipeline Design and Development
...