[whpalmer4]

Can you show us an example? If that task is set (as is the default) to be scheduled as soon as resource availability permits, the task won't be scheduled until that resource is available, or a violation will be flagged if you have scheduled a fixed start time for the task and the resource isn't available at that time.

If your resource is available at less than 100% availability, this will make the duration go up, which will push out the end date, or if your resource is not available for part of the expected time due to a modified work week, that can also cause the end date to be pushed out beyond what you might expect.

If you can put up an example, we can have a look, or you can use the Help->Send Feedback command to send a declassified version of your file to the Omni support personnel and ask them if the behavior you are seeing is anomalous.