Skip to main content
Participant
December 18, 2022
Question

Bridge workflow not working

  • December 18, 2022
  • 3 replies
  • 1795 views

As soon as I start a simple little "save to jpeg" workflow, it gives med "1 error files" and when I open that row I get Reason: Destination Cannot Write and Task: Preprocessing. 

No files are saved/converted. I have run workflows before. I have turned off Ransomeware Protection in Windows. No luck. I'm running Bridge 2023. I have write access to the folder, I usually choose to create a subfolder from the original location.

Any help would be much appreciated.

3 replies

Imaginerie
Community Expert
Community Expert
December 28, 2022

Not saying vthat it is related but I had trouble with exports in the past and it was due to the file handling preferences in Bridge (files too big)

You can also check the cache settings in the preferences as well, just in case.

It might not be it, but worth checking!

Legend
December 27, 2022

Bridge does not work with cloud services. Save to a folder that is not sync'd to OneDrive.

Conrad_C
Community Expert
Community Expert
December 27, 2022

I just got this same Destination Cannot Write error with a Bridge workflow on two different normal (not connected to cloud sync) output folders, one within my home account on my Mac’s internal storage. Bridge has both local Files and Folders access and Full Disk Access set in macOS 12.6.2 on Apple Silicon.

 

So something is going on here that has nothing to do with network/cloud-synced drives and is not specific to Windows or Mac.

 

Edit: I tried the Export panel instead of Workflow. The same file format settings to the same folder that fail in the Workflow workspace, output successfully using the Export panel. So the problem might be specific to Workflow, and a possible workaround is to do the job through Export if possible.

Legend
December 27, 2022

Are you syncing your home folder to iCloud? Can you make changes to files in those folders like adding labels?

Participant
December 23, 2022

I had the exact same issue with Bridge 2023 and I'm running on MacOs Ventura 13.1 with M1 Pro chip.