Unfortunately, I have a timer that is triggering to do one thing and a different path that does another and there is no way to update a variable since they both come from the same path, just different reasons.  Thanks for the suggestion.  I figured I would need to create separate WF's but was hoping someone had found a solution.  And if no solution, hopefully this can lead to us getting this token in a future release.

You want be able to know the workflow service task name that triggered the workflow?

No, the Forms activity name or ID that triggered the Workflow.

The activity that triggers the workflow would be a service task. I expect you're actually asking for the user task that precedes that service task? Why would the user task name be preferable over the form name or the form data?

No, I am referring to the service task in the form that triggers the workflow. My forms process has 2 timer activities that call the same workflow: 

1. I have a timer that sends a reminder every 24 hours if they haven't approved the form.  It also calls a workflow service activity that writes that a reminder was sent into a table variable in the form.
2. I have a timer that runs every 5 days to escalate the form if not approved.  It also calls the same workflow via a different service activity that writes that an escalation happened into the same table variable in the form.

The verbiage written into that variable is different depending on whether it was a reminder or an escalation.  Without knowing the name or the id of the activity that triggered the workflow, I cannot have a routing decision that provides the different verbiage.  Instead I must create 2 different workflows that do identical functions with slightly different verbiage.  I understand this same info exists in other locations but the customer is requiring it be written directly into variables in the form.  Is there a way to tell which Form activity (name or ID) triggered a workflow?

Any word on a way to tell the actual Form's activity that triggered the workflow?  I have another customer that is wanting to trigger a workflow at the start of the Forms process and again at the end of it.  Instead of having 2 workflows that do very little, it would be nice to be able to contain all of the WF tasks that relate to this Form's process within a single WF.

There is no way to know which timer went off to allow the process to continue on to the service task.