Dynamics Community Forum Thread Details

BPF stage duration timer not showing – works on another BPF in the same environment

Hi everyone,

I have two Business Process Flows in my Dynamics 365 environment (Model-Driven App / Power Apps). One of them shows the stage duration timer correctly (for example: "Verificación Contacto Y Empresa (16 Min)"), but the other BPF, which runs on a custom entity called SPC_2 (Carga Protocolo), does NOT show the timer anymore. It used to show it before, but at some point it stopped.

Here is what I see:
- BPF 1 (working): Shows the time in the active stage, e.g. "Stage Name (16 Min)" ✅
- BPF 2 on SPC_2 (not working): Only shows the stage names without any duration ❌

Both BPFs are in the same environment and the same app. I have not changed anything in the BPF configuration recently. The timer just stopped appearing.

I would really appreciate if someone could help me understand:
- Did something change in a recent platform update that affected the BPF timer?
- Is there a setting or configuration I need to activate to get the timer back?
- Is there anything specific about custom entities that could cause this behavior?

I'm attaching screenshots of both BPFs so you can see the difference.

Thanks in advance for any help or guidance!

tion recently. The timer just stopped appearing.

Categories:

Power Platform integration

Hi,

I ran into a similar issue before, and in most cases this behavior is not due to any recent platform change but rather how the Business Process Flow (BPF) is being updated behind the scenes.

The stage duration (e.g., “(16 Min)”) depends on internal fields such as Active Stage, Traversed Path, and Active Stage Started On. If these are not updated correctly, the timer will stop appearing even though the BPF itself continues to work.

Here are a few things I would recommend checking:

Custom plugins / workflows / JavaScript
- Verify that no custom logic is updating fields like traversedpath, stageid, or processid directly.
- Updating these fields manually can break the timer calculation. If stage changes are required via code, they should be done using supported messages like SetProcessRequest or SetActiveStageRequest.
BPF entity data
- Each BPF has its own underlying entity. Check whether the field Active Stage Started On is being populated/updated correctly. If not, the duration will not be shown.
Test with a new record
- Sometimes existing records get into an inconsistent state. Create a new record for the same entity (SPC_2) and move through stages to see if the timer appears there.
BPF versioning
- If the BPF was modified and reactivated, older records may still be tied to a previous version, which can affect behavior.
Reactivation
- As a quick step, try deactivating and reactivating the BPF.

From experience, the most common root cause is custom code interfering with traversedpath or stage updates. Temporarily disabling such logic can help confirm this quickly.

If this helped, please mark it as a Verified Answer, it helps others in the community facing the same challenge!

Quick Links

Leaderboard > Microsoft Dynamics 365 | Integration, Dataverse, and general topics