Child Item

Error path/conflict/folder

Hi, I have an integration that is built inside the Workato Ipaas and I'm receiving an error that says "path/conflict/folder..". I know that if a folder with that name already exists, it will return this error, but inside the integration before going to that action to create a new folder, I have another one to check if a folder with that name already exists, so for me it doenst make sense to return an error inside the create folder step

Find more posts tagged with

API

Abuse

Comments

Greg-DB

If an app attempts to create a folder at a path where one already exists, the Dropbox API will return this error indicating that there's already a folder at that path. There isn't a way to change that particular API behavior, but the app can decide what to do with the error (e.g., to ignore it, or some other error handling behavior), of whether to make the call in the first place.

For instance, an app can check if a folder already exists, and if so, skip the folder creation step. That logic would be under the control of the app itself though.

sarahaidar2

Yes, actually this example I'm already doing. First I check if a folder with that name already exists, if so, the file will be uploaded in this folder, if not, it will create the new folder to then upload the file.

But the integration says that the folder with that name doesn't exits, so that's why it is going to the action to create a new folder. But then returns the error, so for me makes no sense.

If I checked that doesn't exist, why it's not being able to create the folder?

Greg-DB

If "the integration says that the folder with that name doesn't exits" when it does actually exist, there may be a bug in the integration. We can't provide support for third party apps themselves, so you may need to debug that or contact the third party developer for help.

If there seems to be a bug with the Dropbox API itself, please share the details so we can take a look. In that case, it would be best to open an API ticket with the following details:

the account ID of the affected account
the name and version number of the SDK/library you are using, if any
the steps to reproduce the issue, including relevant code snippet(s), but don't include any access or refresh token(s)
the full text of any error or unexpected output