Testing Buttons
You must test Add Button actions in each state where you want the button to appear. For example, if you want a Close Order button to appear on a record form as it moves from state to state, you must add the Add Button action for the Close Order button to every state in the workflow. If you only add it to the first state, the button does not appear on any subsequent state in the workflow.
You can use the workflow execution log to test the context of the record and make sure that the triggers for the Add Button action are set correctly. For example, a workflow initiates on an After Record Submit trigger, indicating the user clicked Save on the record. The workflow does not execute any actions set to trigger before the After Record Submit trigger executes. Since the Add Button actions are set to trigger on Before Record Load, which occurs before the After Record Submit trigger, the workflow does not execute the Add Button actions.
In this example, you can change the workflow initiation trigger to All or Before Record Load. You could also redesign the workflow so that the record enters the state with the Add Button actions on a Before Record Load or Entry trigger.
If you create a workflow that includes an Add Button action, when a user interacts with the button and the record is saved, the System Notes will list the role of the user as Administrator, regardless of the role the user is logged in as. This behavior is expected and is not related to the Execute As Admin property on the Workflow Definition page.