Why can't AutomatedOn read from my data source?
These errors mean AutomatedOn couldn't fetch records from your data source, either for the process's dataset or for a rule's lookup.
Errors appear on the process's Test tab, in the step details on the History tab (click a red step badge), and on the dashboard (hover over the ! pill). In the messages below, … stands for a name, address or value from your own set-up.
Settings missing
| Message | What to do |
|---|---|
OData Endpoint is not set on the data source. | Open the data source in the back office, fill in its endpoint, then save and publish. |
Entity Set is not set on the dataset. | Open the dataset and fill in Entity Set. |
Base URL is not set on the REST data source. | Open the REST data source and fill in its base URL. |
Dataset not referenced on process. | Pick a Dataset on the process. |
Data source for this dataset was not found. | The dataset must sit directly under a data source in the back office. |
Names and paths that don't match
| Message | What to do |
|---|---|
Entity set '…' was not found in the OData metadata. | The entity set name doesn't exist in that API. Check the spelling and capitals, or pick it from the list in the back office. |
Items path '…' was not found in the response. | The REST dataset's items path doesn't match the shape of the response. Check the API's response and correct the path. |
Items path '…' points to a … value; it must point to an array or object. | Point the items path at the list of records, not a single value. |
The response from '…' was not valid JSON: … | The API didn't return JSON. Check the address and resource path, and that the API is working. |
The data source returned an error
On the Test tab this looks like Data source query failed (401): …. In run history it looks like Data source query to '…' failed with status 401. Response: …. The number is the status from the other system:
- 400: the query wasn't accepted, often a filter with a typo or a field that doesn't exist. Copy the URL from the Queries tab to check it. In a scheduled run, a 400 is retried automatically (Retry scheduled).
- 401 or 403: the sign-in was refused. AutomatedOn already refreshes the sign-in and retries once on a 401. Check the API Auth Profile with Test Connection, and contact Three 17 support if the credentials need changing.
- 404: the address or entity set doesn't exist.
- 500 or above: the other system had a problem. Try again later or contact whoever runs that system.
Other messages
REST dataset paging stopped after 1000 pages without reaching the end. …: the paging settings never find the last page. Check the pagination settings, or add query parameters that fetch fewer records.Refusing to follow the next page link to '…': it isn't on the data source's host.: the API's next-page link points to a different site, which AutomatedOn won't follow. Contact Three 17 support.Refusing to connect to '…': it resolves only to a private, loopback, or link-local address.: AutomatedOn can only reach addresses on the public internet. Use a public address for the API.