When you manually edit and save the "Status" field, the flow fires correctly, this means there is nothing wrong with the configuration of the flow. In your case, the process builder did not trigger the flow.

A process builder field update does not trigger a "before flow" in the same transaction. A process builder field update will only cause the before trigger, after trigger and workflow rule to re-execute.

The order of execution is the reason.

1. Manual updates the A2D record
2. Before Flow runs (this is prior to the process builder execution)
3. Before and After triggers execute
4. Workflows Execute
5. Process Builder Executes (causing #3 and #4 to re-execute)
6. After Insert/Update Flow executes
7. Record is saved to the database.

Hence you can see that your flow won't execute due to process builder field update in the same transaction. If you change your flow to After Insert/Update then you will see the desired result. Please try.

Lastly, it is extremely bad practice to have multiple automation per object, mixing process builder, flow, workflow and triggers. I will recommend using only one type of re-architecting this. Iff this object has triggers, then any field update logic should be made inside the triggers.

When you manually edit and save the "Status" field, the flow fires correctly, this means there is nothing wrong with the configuration of the flow. In your case, the process builder did not trigger the flow.

A process builder field update does not trigger a "before flow" in the same transaction. A process builder field update will only cause the before trigger, after trigger and workflow rule to re-execute.

The order of execution is the reason.

1. Manual updates the A2D record
2. Before Flow runs (this is prior to the process builder execution)
3. Before and After triggers execute
4. Workflows Execute
5. Process Builder Executes (causing #3 and #4 to re-execute)
6. After Insert/Update Flow executes
7. Record is saved to the database.

Hence you can see that your flow won't execute due to process builder field update in the same transaction. If you change your flow to After Insert/Update then you will see the desired result. Please try.

Lastly, it is extremely bad practice to have multiple automation per object, mixing process builder, flow, workflow and triggers. I will recommend using only one type of automation and re-architecting this. Iff this object has triggers, then any field update logic should be made inside the triggers.

When you manually edit and save the "Status" field, the flow fires correctly, this means there is nothing wrong with the configuration of the flow. The process builder did not trigger the flow.

A process builder field update does not trigger a "before flow" in the same transaction. A process builder field update will only cause the before trigger, after trigger and workflow rule to re-execute.

The order of execution is the reason.

1. Manual updates the A2D record
2. Before Flow runs (this is prior to the process builder execution)
3. Before and After triggers execute
4. Workflows Execute
5. Process Builder Executes (causing #3 and #4 to re-execute)
6. After Insert/Update Flow executes
7. Record is saved to the database.

Hence you can see that your flow won't execute due to process builder field update in the same transaction. If you change your flow to After Insert/Update then you will see the desired result. Please give this a try.

When you manually edit and save the "Status" field, the flow fires correctly, this means there is nothing wrong with the configuration of the flow. In your case, the process builder did not trigger the flow.

A process builder field update does not trigger a "before flow" in the same transaction. A process builder field update will only cause the before trigger, after trigger and workflow rule to re-execute.

The order of execution is the reason.

1. Manual updates the A2D record
2. Before Flow runs (this is prior to the process builder execution)
3. Before and After triggers execute
4. Workflows Execute
5. Process Builder Executes (causing #3 and #4 to re-execute)
6. After Insert/Update Flow executes
7. Record is saved to the database.

Hence you can see that your flow won't execute due to process builder field update in the same transaction. If you change your flow to After Insert/Update then you will see the desired result. Please try.

Lastly, it is extremely bad practice to have multiple automation per object, mixing process builder, flow, workflow and triggers. I will recommend using only one type of re-architecting this. Iff this object has triggers, then any field update logic should be made inside the triggers.