DataSync FAQs and Frequent Errors

What does it mean when I get a 403 Forbidden Error?

The HTTP/1.1 403 Forbidden error is most commonly caused by an issue with your credentials in Datasync. If you've received this error, we suggest verifying your credentials and app token and trying to run the job again. 

Please note that when a user inputs incorrect credentials 3 times, they will be locked out of their account for 30 mins and subsequent login attempts are blocked. 

If this is the case, we suggest waiting 1 hour before attempting any other updates. Then log in to your Socrata domain to confirm your username and password. Once you have verified your login, copy/paste your username and password into the Datasync job's credential area and make sure the app token is correct and specific to your Socrata account.

I'm getting a connection error when trying to use DataSync. What's going on?

There are a number of factors that contribute to your ability to successfully run a DataSync job. Common issues we see include network/firewall issues and security issues related to outdated Java versions or TLS settings.

Network/Firewall Issues Troubleshooting

The first test to try to ensure there is no issue with your network settings or firewall is to run a simple command in your command window (Run -> cmd in Windows, using the Terminal application in Mac):

ping {{domain}}

For example, if the domain you have configured in DataSync is, you'd run:


If you see a message like "request timeout", "connection timeout", or "could not resolve", that indicates that something at the network level is probably blocking the connection to your Socrata domain. You should reach out to your IT/networking folks to determine why we are being blocked.

Java Version and TLS Issues

Open a command window and run:

java -version

If you see anything other than a version starting with "1.8....", you will need to upgrade your Java per our list of supported secure integration clients.

I'm getting a "Job complete with errors: FAILURE Processing [dataset name and column name] uninterpretable as money in input" error. What's the issue?

Numeric and money data types need to be ingressed without a dollar sign ($). Excel may automatically add this formatting to columns configured as "Currency." Changing the column type to "Number" in Excel should remove this formatting. If the formatting exists elsewhere in your automation workflow, it will need to be removed.

I ran a datasync job on my dataset and it completed successfully. However, the update date on the dataset has not changed?

If the data that is uploaded has no differences from the dataset online, the update date will not change on the dataset. Datasync will only update your data if there are differences in your source file and the published dataset. 

If the above steps do not yield any helpful insights, please submit a ticket to, and we can assist with further troubleshooting.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request



Article is closed for comments.