Resolve Import Issues

The most common causes for error during imports and how to fix them.

Conserv designed the import process to be hassle-free, but sometimes issues may arise. Review the following information for details. Here are the most common issues.

Table of Contents

• Errors in the original import file
  • General errors
  • Time zone errors
  • Commas instead of periods for decimal notation
  • Special characters or emojis in unexpected places
  • Date-Time formats that are not supported
  • Wrong CSV encoding
  • Files that are too large
  • Multiple files with formats that are not identical
  • Import does not fail but graph looks strange
• Browser errors
• Heavy server traffic or local network errors
• Errors that can be ignored
• Upgrade to Conserv sensors
• Support

Errors in the original import file

General errors

Errors may include, but are not limited to:

• sudden date changes or formatting changes
  Example: After the last reading on January 9th, the format changes to accommodate the 2 digit day. It changes from M/D/YYYY to M/DD/YYYY. The import flow allows you to pick one format only. If that format changes in sections of your file, the software will ignore all the rows that don't match. This will also apply if you have months changing from single to double digit and a format that does not remain consistent.
• empty rows
• empty columns in the middle of the data
• empty cells (missing temperature or RH reading in a row)
• inconsistent units of measurements

Time zone errors

If you live in a region that enforces Daylight Savings or Summer Time Savings, your files may either skip or duplicate a reading. This can cause them not to show up in the graph or cause a whole batch of rows to fail upload, creating a large gap in your graph. If you upload a file that spans the time zone change date, sections of your graph can also be 1 hour off.

Commas instead of periods for decimal notation

Commas can be interpreted as separators in csv files and will split your data in strange places. If your file uses commas for decimals (for example, 38,75 instead of 38.75), change all of the commas to points before you import your files.

Special characters or emojis in unexpected places

Any unusual character such as accented letters if your file includes the name of sensors in other languages might cause reading errors. Remove special characters in files to make sure they are not the source of the errors.

Date-Time formats that are not supported

The date-time format chosen, for example DD/MM/YYYY HH:mm must match your timestamps exactly. Even a difference of a single space in the wrong place will cause the import to fail.
Did your import succeed but the graph looks strange? Go back to your source file. Is the error in the file?

Is your date-time stamp missing the time? The new import flow requires time to be set in the date-time stamp (in order to match time zones). If you do not have a time in your original data, add an approximate one.

If you still have trouble, try using the 2025 Conserv Import Template and use the same datetime formatting.

Wrong CSV encoding

Conserv Cloud requires .csv files with standard UTF-8 encoding. If you try to upload a csv file with the wrong type encoding, it can fail. See, for example, this file from an Other Logger brand that has been saved in UTF-16 LE encoding.

To check what kind of csv file you have, open it in Notebook or other similar alternative. If you are still unsure, make sure have exported your file as UTF-8 or convert it before you try to upload.

Files that are too large

Be aware that Conserv SCS devices are set to take readings every 15 minutes. We do not recommend uploading data logger files with intervals lower than 10 minutes as data-heavy files can cause problems. Avoid uploading single files with more than 30,000 rows of readings. They should still work, but you will need to wait several minutes for the import to complete.

Multiple files with formats that are not identical

If you are a Conserv customer with a paid subscription, you can use the multi-file import to import up to 20 files at a time. If you have more files than that, you must perform multiple imports. However, if your files do not have consistent formatting, they will fail.

• Any minor difference including column names, spacing, order, etc. will cause an error.
• Any differences in data formatting across files may also cause an error.

Find the "bad" file by importing in smaller groups. All files with identical column formatting will upload successfully. Any grouping that includes the "bad" file will fail.

Import does not fail but graph looks strange

If your graph does not look right, go back to the original import file.

• Did you pick the wrong time zone?
• Is the "strange" data also in the original file?
• Is the "strange" data real? Did your spaces experience an unusual situation that you had not noticed before?

Browser errors

Check that you have whitelisted the Conserv.io domain because some ad blockers or pop-up blockers may interfere with the import process. For instructions on how to whitelist Conserv.io, consult your browser or security product’s documentation. If you have a browser extension that blocks ads or pop ups, and your import fails, disable the extension and try again.

Try switching browsers. Chrome or Edge work best.

Heavy server traffic or local network errors

Certain times of the week and of the month are heavy import times. Many users import their data at similar times on Mondays or Fridays, or at the beginning or end of the month. If your imports fail, and none of the reasons above apply, try at a different time of day/week/month.

Any issues with your local server, network, or internet may also interrupt the importing process. Ask your local support or IT department if there are any current issues with your network. Try again in a few hours or when you have confirmed the issue is not on your end.

Errors that can be ignored

Depending on your file type, you may have:

• One or more summary header rows with information
• One or more end rows with calculations such as averages or standard deviations
• Rows in the middle or at the end of your file that say Logged instead of having numbers (especially with HOBO loggers)

These rows will show up as Errors in the summary of your import. If the number matches the number of summary or empty rows in your file, you can ignore them.

Upgrade to Conserv Sensors

Are you tired of importing sensors all the time? Reach out to us about upgrading your system to Conserv for real-time alerts and a proactive environmental monitoring program.

Support

If you have import issues after trying these solutions, please create a support ticket.

• Attach any csv files you were attempting to import.
• Include any screenshots of error messages.
• Tell us what brand of data logger your file is coming from.
• Tell us what troubleshooting steps you have already tried.

This will help us troubleshoot faster.