...
| Expand | ||
|---|---|---|
| ||
Some accounts may have a fixed time for refresh tokens, such as Google accounts must 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
...
| Expand | ||
|---|---|---|
| ||
Data preview is limited to the first 50 records that are pulled in. All subsequent data previews down the pipeline will work only with that initial preview data set, so your actual resulting data may vary from what you see in the preview data. |
| Expand | ||
|---|---|---|
| ||
Because Pipeline Validation is intended for Pipeline development and testing, we recommend disabling Pipeline Validation in Manager > Settings for your production Orgs. You can always manually run Pipeline Validation for individual pipelines in Designer. |
| Expand | ||
|---|---|---|
| ||
When a pipeline is called in response to an event, the caller has to wait for the response until the entire pipeline completes. If the pipeline is large and takes a long time to complete, the caller may time out and mark a failure even though the pipeline is still running and processing data. Pipelines called in response to HTTP events should not process the data. They should provide status about whether data was “accepted” or not, but leave the “processing” of data to another asynchronous or scheduled pipeline. |
...
| Expand | ||
|---|---|---|
| ||
Accidentally deleting or making serious blunders in a pipeline could result in days of lost work. Some general guidelines for pipeline backups include exporting pipelines after significant milestones (major changes, a new release), renaming the pipeline file (.slp) to indicate the event, and storing the exported pipelines in a repository. For example, you can backup your assets such as pipelines, files, accounts, and tasks to GitHub repositories using your SnapLogic account. For more information, see SnapLogic - GitHub Integration. |
| Expand | ||
|---|---|---|
| ||
When pipelines tasks are configured to schedule pipeline runs or allow them to be triggered, you can have notifications sent when the task has started, completed, failed, or stopped. |
...