Monad error messages
The phrase “Error during execution of task” has been removed from many of these error messages. You should remove it from your search string to find the error description you need.
Some reference tasks failed.
One or more of the subtasks in this sync sequence did not complete successfully.
Trigger was ‘all_successful’ but some of the upstream tasks failed.
One or more of the subtasks in this sync sequence did not complete successfully.
HTTPError 404 Client Error: Not Found for url
Monad can’t connect to the service, usually because of an error in the resource domain or port.
No upstream states can be mapped over.
The task is blocked because it depends on one or more prior tasks that did not complete.
Skipping dbt run
This is a status message, not an error. No new data was detected, so no data model changes are required.
Ready to proceed with mapping.
This is a status message, not an error. The data was successfully extracted, and is ready to process.
HTTPError: 401 Client Error
401 error (Unauthorized) when loading the connector. This usually means that there was a problem with the provided authentication method. Check that the service user name and password, or API key and token, are correct, and are provisioned with the correct access to allow Monad to read your data.
HTTPError: 429 Client Error: Too Many Requests
The connector has made too many requests and is being rate limited.
ClientError: An error occurred (UnauthorizedOperation) when calling the DescribeRegions operation.
The credentials specified are not authorized to perform this operation.
AccessDeniedException: An error occurred (AccessDeniedException) when calling the DescribeAccount operation.
The credentials specified don’t have permissions to access this resource.
This page was last modified: 4 Nov 2021