Error Fallback cloud flow should be a child

In order to prevent asking the user for permission, this cloud flow should be triggered by another new cloud flow.

Then, we can add the parent cloud flow to the different apps.

Start by locating the Error Fallback cloud flow and the other cloud flows used by the different apps. Trace how the flow currently requests permission and how flows are related. Done means the Error Fallback flow is triggered as a child by a new parent cloud flow and the parent can be added to the relevant apps without prompting the user for permission.

Written by the indexing model from the issue text.