I am having an very rare issue with a workflow where it is supposed to go from Pending to Rejected (id:3). It says it's doing it, but the field doesn't change. I have tried to replicate this in sandbox, but it always works. It works for the user most of the time as well. I have checked the workflow and roles, but I am at a loss of what to check since I can't replicate the issue. Anyone have any tips or experience something similar?

Are you doing this using a Button labeld "Reject" which when clicked transitions to the Rejected state, then On Entry of your Rejected State setting the Approval Status field value?

it transitions to a rejected state and sets the field on entry

I had the exact same issue in August of last year. I walked support through it and they couldn't give me an answer, and in the end just gave up.

Usually when this is the case it's because a user is working in the WF without the proper permissions. So the WF fires but because of some other error it doesn't perform the action

Im about to double check that prod roles and sandbox roles are the same because its one of the other things i just thought of that I didn't check

The other option is another action in that state is erroring out so that action cannot be fully completed.. like a Send Email where the receipient or Sender is Inactivated or doesn't have a valid email something like that is common

its just a sets 2 fields and does send an email

if you check the Show Rejected action under the WF log does it show any more infomration or errors?

I mean I don't know the specifics of your case, but with mine, we literally check EVERYTHING. Workflow was running as admin, no inactive entities, no period issues, etc., etc. As far as I and NS support could tell (and I'm no newbie at this stuff, been doing implementations for 10+ years), we were able to replicate the conditions exactly in sandbox and it ran fine there and actually executed the change.

@MGBC no errors it says approval = 3 and that it executed and there are other warnings/failures on the list. @James Morris yea that's where I feel like I am. I have checked a lot and it's such a simple change for the workflow that I am not sure why it would error.