Flow Diagnose

Open

The reset action was configured to continue if sharing errors occurred. But the sharing action was not so flexibly configured. Skipping the next, unsharing, actions.

Result differences

• Success. A successful action will let the process continue and execute the next consecutive action.

• Warning: An action with a warning shows the warning message and skips the process to continue with the next consecutive action. Some actions allow the process to skip with a warning such as:

  • Sharing actions. Sometimes you don’t know if a folder can be shared with a user. Especially when you loop over a list of users. i.e. account team members. And not all of those users made the connection with SharePoint yet. In this case, you want to configure the action to skip the action instead of stopping the whole process.

  • The reset action will fail by default if the running user does not have sharing rights. An option exists for this action to skip itself if sharing rights are missing.

  • The create folders also have a reset component just like the reset action. Enabling the reset also can skip the process (only the reset component, not the creation) if sharing rights are missing.

• Error: An action that has failed due to implementation/user error/Salesforce limitation/SharePoint limitation/Filenize error will stop the action and all consecutive actions. Effectively stopping the whole process. Only processes linked to the same record are stopped, ensuring other processes running in the same transaction carry on.

• Skipped: An action that was not (fully) processed due to an error in the process or a previous process.

• Pending: An action that is still waiting to be processed. When using Queueable Groups, actions will stay in their pending state until all previous actions and processes are completed.

Actions in scope

In the Flow Diagnose UI, you might see that some actions have a border around their icons. This is to indicate that these actions are linked to the current Salesforce record. Some processes go beyond the record. i.e. creating an account folder, opportunity folder, and a quote folder in one hierarchy. They would still show in the Flow Diagnose UI because of its dependency, but might not be within the scope of the current record. These actions that are from a different record would not indicate a border.