"Provoke" Macro doesn't always perform "Provoke" action

[Laraul]

Time: Any time
Frequency: Occasionally
World name: Hyperion
Character name: Laraul Lunacy
NPC name: Any
Monster name: Any
Class/Level: PLD/50
Party or solo: Party
In-game time: Unknown
Area and coordinates: Any location/instance/RAID
Steps
1. Create the following macro and test it repeatedly. (Windows version)

/macroicon Provoke
/macrolock
/macroerror on
/action Provoke
/party Provoke (<recast.Provoke>)  <t>

The proceeding macro doesn't always activate the "Provoke" action when triggered. Occasionally there are times I must repeatedly press it before it performs the "Provoke" action. When this happens I see the following in my log window.

[10:50](Laraul Lunacy) Provoke (--:--)  Nael deus Darnus <se.13>
[10:50](Laraul Lunacy) Provoke (--:--)  Nael deus Darnus <se.13>
[10:50](Laraul Lunacy) Provoke (0:40)  Nael deus Darnus <se.13>

This text is generated by the last line. It shows my target, and the recast time for the action "Provoke." "(--.--) = no recast, (0:40) = 40 seconds until next use (i.e. just activated)" I never see any error message explaining why the action didn't perform properly.

When I use the action only (no macro) it ALWAYS activates.

This is the only macro I have that is not working properly. It's been an issue for quite sometime (almost a year since I first encountered it). I've tried making minor alterations, hoping I could get it working every time instead of 50/50. Nothing I've tried works.

Here's an image of the macro for reference.

[monochromicorn]

Your problem is incredibly obvious: it's a macro

Editing to elaborate.

Macros are prone to error. If you just happen to be in an animation from a previous move, macro errors. If you dont put in wait times, macro errors. And the macro can error just because it's unreliable. There is a reason macros are discouraged in this game, they are so error prone that people press them several times just to make sure they go off right.

[Mholito]

Basically: Macro's don't queue skills. A maro will try to perform each step in quick succession. If any action can't be performed the exact moment the macro tries to use it, it will be skipped.
Using skills outside of macros cause them to be "queued" for a short amount of time. This means that they will be used as soon as they are available after you press the button.

[Duuude007]

To add to this, any macro used can cause the sequence of actions by another macro to be cancelled. This means that unless provoke was the first action, there is risk of failure.