If an error message displays while you use CloudWorks, review the list of common scenarios to find a resolution.
Errors with exports of .csv or .txt
Solution: add .csv or .txt to your export filename. This ensures your export can be loaded into AWS S3 with the proper file type.
Error in integration list display
Solution: if you do not see your complete list of integrations after you switch your Workspace, you can either click the refresh icon next to Integrations, or refresh the browser.
Export issue: header information and no data included
If your export only includes header information, and no data, this means that you do not have Internal (Full Access) granted to that list.
Solution: make sure that your workspace administrator has granted Internal (Full Access) to the list associated with your export. See Create a new integration.
Export and Selective list access issue:
- When multiple people have Selective Access set to a list, and
- When your workspace administrator grants Internal (Full Access) to the list associated with your export, an issue may arise wherein they need to regrant user access
Solution: your workspace administrator should copy both the Write and Read data from the list's user settings, and replace this data when they've granted Internal (Full Access) to the list.
Errors with model-to-model import actions
CloudWorks does not support model-to-model imports.
- If your process contains only a model-to-model import, you'll get this error:
Connection and Data source/Target should be specified for at least one Process step.
- If your import completed with failures:
Partial failure of import action, mismatch of data types.
- If your process includes a cloud source action as well as a model-to-model import, you'll get an error.
Also see Integration notifications.