The find entry is the first activity in the workflow and yes the workflow terminates. No other activities process.

No, the activity does not find the entry. The error this activity produces is pasted above and here as it throws two errors.

I've exported the workflow and confirmed the correct value was being stored in the xml, reimported, and still get the same error.
Right now I disabled the Find Entry activity and replaced it with an advanced search syntax activity to use the 6250 entry ID and configured the other activities to use the result of this instead of the find entry activity. This workaround was successful but not desired.
