Wrap every data operation and cloud flow run into an `IfError` statement
Open
Scheduling tool
- Dominant language
- C#
- Stars
- 135
- Forks
- 260
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 143
Description
In order to improve error handling, and avoid issues on PROD, we should wrap every dataverse and cloud flows call into the try-catch equivalent for PowerApps, and then implement the corresponding logic if an error occurs.
This has to be done in every meeting type:
- [ ] Informational
- [ ] API Review
- [ ] SDK Review
For more context, see https://github.com/Azure/azure-sdk-tools/issues/3956
Contributor guide
Research direction
Start by inventorying the Dataverse and cloud flow calls used by the Informational, API Review, and SDK Review meeting types. Read issue #3956 for context, then define the error behavior for each call before implementing and verifying all three flows.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100