Bad gateway, creating folder

[epsien]

I made a simple flow to create folders. It worked fine for a while, but now i am getting this error message:

Any idea how to fix this?

{

"error": {

    "code": 502,

    "source": "europe-002.azure-apim.net",

    "clientRequestId": "fe2b4965-be8b-40f0-82bb-42e50b5a783d",

    "message": "BadGateway",

    "innerError": {

      "status": 500,

      "message": "The filename, directory name, or volume label syntax is incorrect. (Exception from HRESULT: 0x8007007B)\r\nclientRequestId: fe2b4965-be8b-40f0-82bb-42e50b5a783d\r\nserviceRequestId: fe2b4965-be8b-40f0-82bb-42e50b5a783d"

    }

  }

[Brad_Groux · Accepted solution]

Error codes 500 or 502 are temporary or transient failures, such as a service blip or outage. Click or tap Resubmit to try the flow again (source).

👨🏻‍💻 If this reply answers your question or solves your issue, please ACCEPT AS SOLUTION ☑️. If you find this reply helpful, please consider giving it a LIKE 👍.

[v-bacao-msft]

Hi @epsien ,

Could you consider sharing the Flow run history?

Now that the error message has mentioned "The filename, directory name, or volume label syntax is incorrect.", Have you checked the corresponding configuration?

You could add Compose above the Create new folder action to output the value you configured in the Folder Path field and see if it meets the requirements.

Best Regards,

[epsien]

Flow run history like this?

Pretty sure it meets the requirements. Worked for a while. Then it started failing.

Mislykket = Fail

Vellykket = Success

30. jan., 15:16 (20 t siden)

00:11:05

Mislykket



30. jan., 13:08 (23 t siden)

00:14:06

Mislykket



29. jan., 11:16 (2 d siden)

00:14:16

Mislykket



29. jan., 10:54 (2 d siden)

00:13:29

Mislykket



29. jan., 08:33 (2 d siden)

00:14:04

Mislykket



28. jan., 14:24 (2 d siden)

00:11:41

Mislykket



28. jan., 10:37 (3 d siden)

00:13:14

Mislykket



24. jan., 11:35 (1 uke siden)

00:00:29

Vellykket



24. jan., 11:24 (1 uke siden)

00:13:21

Mislykket



24. jan., 11:22 (1 uke siden)

00:12:05

Mislykket



20. jan., 12:48 (1 uke siden)

00:00:28

Vellykket



17. jan., 07:41 (2 uke siden)

00:00:41

Vellykket



17. jan., 07:15 (2 uke siden)

00:12:43

Mislykket



16. jan., 13:29 (2 uke siden)

00:00:29

Vellykket



10. jan., 14:29 (2 uke siden)

00:00:27

Vellykket



10. jan., 14:22 (2 uke siden)

00:00:28

Vellykket



10. jan., 14:18 (2 uke siden)

00:14:32

Mislykket



9. jan., 13:22 (3 uke siden)

00:00:29

Vellykket



8. jan., 14:25 (3 uke siden)

00:13:06

Mislykket



8. jan., 12:12 (3 uke siden)

00:00:28

Vellykket



8. jan., 12:10 (3 uke siden)

00:00:29

Vellykket



6. jan., 12:46 (3 uke siden)

00:00:30

Vellykket



2. jan., 13:56 (4 uke siden)

00:00:30

Vellykket



2. jan., 11:10 (4 uke siden)

00:00:28

Vellykket

[dwats01]

I had this issue, for no reason on one run only.  After much deliberating, it turns out the input I was taking had a trailing space that was virtually invisible, and the flow didn't like that space in the filepath.  Always use trim() if you take inputs from users.  🙂