Axios 409 Error Saving Workflow with SharePoint Connector

[anthonywhite]

Describe the Bug with repro steps

1. In VS Code create workflow
2. Add Request Trigger
3. Add SharePoint HTTP Request action with existing SharePoint API connection from Azure
4. Save workflow. If API connection in Azure has a read-only lock, Axios 409 error results
5. If Azure resource lock changed to delete from read-only, workflow save will work

What type of Logic App Is this happening in?

Standard (VSCode)

Are you using new designer or old designer

New Designer

Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg

No

Workflow JSON

No response

Screenshots or Videos

No response

Browser

N/A - design time issue

Additional context

Just reporting this in case a) it help others or b) a more precise error message might be shown

AB#26890250

[ccastrotrejo]

Hi @anthonywhite thanks so much for raising this issue. I tried to repro in different ways but I couldn't. I added multiple locks and tried with different API connections. I might not be doing it in the right way. am doing it wrong. Could you explain a little bit more on how you added an existing SharePoint API connection from Azure into your local workflow? I also have some questions

• Which version of vscode extension are you using? Could you try with the latest?
• Is this problem also occurring within the portal?

[ccastrotrejo]

@anthonywhite I was able to repro the issue. There are a few notes about this.

• Since the lock is for read-only. It does makes sense that the service doesn't allow to create new connections and therefore not allow to save the workflow
• The vscode extension is showing what we are getting from the backend API call response when we call it, plus an insight that the error was when fetching the connection.
• If we desire the get a more precise error message, we might need to move this issue to backend engineers

[github-actions[bot]]

This issue is stale because it has been open for 45 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 14 days since being marked as stale.