AE Sticking in Section/Step -- Why?

I have a custom AE. I have run it many times. However, all of the sudden, it is getting "stuck" on a Section/Step. I have even deleted the step, and created it again, but it is still getting stuck at the same Section/Step. The Step is a SQL Action: UPDATE %Table(ZAR_ORPS_STG) SET Z_STATUS = 'OPEN'. The SQL works when I run it outside of PeopleSoft. Has anyone had this issue? Can anyone explain why this is happening? We are in System Test and desperately need to figure out this issue.

What do you mean by it gets "stuck"? Is this that it takes the step a
long time and you just cancel it out, or does it give an error?
Rebuilding stats might fix it, but I have never seen a simple UPDATE
like this affected by stats...usually it is a SELECT that joins larger
tables that can be fixed by rebuilding stats...

But, if you do try adding the %UpdateStats, don't forget to set the
previous step to 'After Step' on the Commit

What I mean by "stuck", is it takes the step a very long time and does not error. I have to cancel the AE. I tried updating stats, but it is still getting stuck at that same step. Any other ideas? I wonder what I am doing wrong?

What I mean by getting "stuck" is that it stays at Processing on that step. I tried to Update Stats, before that table, but it is still getting "stuck". However, I did notice that in the log, it is getting past that step, but does not inserting data from a file in a subsequent step. There is currently one row of data in the table, and I am trying to insert additional data from a file, using a File Layout object definition. Can you think of anything else that I might be doing wrong?

I is working again, now. I changed some code around in the File.ReadRowset, and that may have been my issue. Thank you for ALL OF YOUR RESPONSES!! It is nice to have this type of forum and I appreciate it very much!

just a suggestion.. instead of using UPDATE %Table(ZAR_ORPS_STG) ... I
might just write the update like a normal sql... when you right click
on your update%Table -- will it resolve the meta-sql? This may not be
an issue with your target table. If I were desperate - that is what I
would do.