SOLVED

Bad Request Error in Flow in fetching Email from O365

%3CLINGO-SUB%20id%3D%22lingo-sub-4630%22%20slang%3D%22en-US%22%3EBad%20Request%20Error%20in%20Flow%20in%20fetching%20Email%20from%20O365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4630%22%20slang%3D%22en-US%22%3E%3CP%3EBelow%20error%20in%20Flow%20%22On%20New%20Email%22%20action%20and%20the%20worst%20part%20is%20the%20error%20in%20random.%20How%20do%20we%20troubleshoot%20with%20a%20vague%20message%20like%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CUL%3E%3CLI%3E%3CSTRONG%3ECode%3C%2FSTRONG%3E%3CDIV%20class%3D%22msla-monitoring-parameters-list-item-value%22%3EBadRequest%3C%2FDIV%3E%3C%2FLI%3E%3CLI%3E%3CSTRONG%3EMessage%3C%2FSTRONG%3E%3CDIV%20class%3D%22msla-monitoring-parameters-list-item-value%22%3EHttp%20request%20failed%3A%20the%20timeout%20was%20reached.%3C%2FDIV%3E%3C%2FLI%3E%3C%2FUL%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-4630%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Flow%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-5074%22%20slang%3D%22en-US%22%3ERe%3A%20Bad%20Request%20Error%20in%20Flow%20in%20fetching%20Email%20from%20O365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-5074%22%20slang%3D%22en-US%22%3ELets%20wait%20for%20the%20matured%20product%20before%20they%20introduce%20new%20product%20for%20same%20purpose%20%3Ap%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-4679%22%20slang%3D%22en-US%22%3ERe%3A%20Bad%20Request%20Error%20in%20Flow%20in%20fetching%20Email%20from%20O365%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-4679%22%20slang%3D%22en-US%22%3EJust%20remember%20that%20Flow%20is%20at%20very%20early%20stages%20and%20there%20are%20a%20lot%20of%20areas%20of%20improvements...being%20said%20that%20I%20hope%20someone%20from%20the%20team%20can%20advice%20you%20how%20to%20troubleshoot%20issues%20with%20Flows%3C%2FLINGO-BODY%3E
Contributor

Below error in Flow "On New Email" action and the worst part is the error in random. How do we troubleshoot with a vague message like this?

 

  • Code
    BadRequest
  • Message
    Http request failed: the timeout was reached.
2 Replies
best response confirmed by Rashid Mohammed (Contributor)
Solution
Just remember that Flow is at very early stages and there are a lot of areas of improvements...being said that I hope someone from the team can advice you how to troubleshoot issues with Flows
Lets wait for the matured product before they introduce new product for same purpose :p