Skip to main content

10.24.4 - Excel CSV accented characters and job status retries

What's new​

Accented characters in CSV files saved by Excel​

Excel for Windows saves "CSV (Comma delimited)" files in the Windows-1252 encoding rather than UTF-8. Jetstream read every file as UTF-8, so characters like é reached Salesforce as � with no warning and no setting to change it. Text files are now decoded the way Excel and Data Loader open them:

  • A UTF-8 or UTF-16 byte-order mark picks the encoding, as before.
  • A file without one is read as UTF-8 when it is valid UTF-8, and as Windows-1252 otherwise.

Job status checks retry after a dropped connection​

Status checks for bulk API jobs (Load Records and Update Records), metadata deployments and metadata retrievals are read-only. A check that fails because of a dropped connection, a rate limit or a server error is now repeated after the usual poll interval, up to three attempts in a row. Previously a single failed check ended polling and reported the job as failed even though Salesforce was still running it.

Check status again for mass updates​

In Update Records and in Bulk Update from query results, a job whose status checks keep failing now keeps its last known state and shows a Check status again button that resumes polling. Previously the job was marked as failed and every unfinished batch as not processed. Results that arrive after resuming are not added to Data History, which already recorded the run as incomplete.

Salesforce API version 68.0​

The Salesforce API version was updated to 68.0 (Winter '27) for all connected orgs, which lets queries use Salesforce's FORMULA() filter function on orgs that support it.

Other fixes​

  • Fixed an issue in the web app, seen in Safari, where every save or update was rejected after the app sat idle, until you logged out and back in.
  • When the connection between Jetstream and Salesforce drops, the web app now reports that the connection failed and is usually temporary, instead of a bare "fetch failed" error.