I am trying to import an application into a QA environment from a Development en

Are the environments all running the same version of Appian?

Yes, all versions are running 7.10

Do you have access to the logs for the environment with the issue? If so, I would recommend trying the import while tailing (watching) the logs. Specifically the application server log. My guess is that something is going a rye on the import.

Thanks for the advice, mpontius! I'm checking out the log now, and I just see the below error repeatedly popping up:

ERROR com.appian.dl.repo.es.LoggingBulkResponseActionListener - The following bulk request failures occurred in the last 60 seconds. Summary: [opType=index, index=designer-objects-ia, type=DT-10, status=SERVICE_UNAVAILABLE, count=2, firstMessage=UnavailableShardsException[[designer-objects-ia][0] Primary shard is not active or isn't assigned to a known node. Timeout: [1m], request: org.elasticsearch.action.bulk.BulkShardRequest@287b978f]].For detailed information about each failure, enable DEBUG logging.

This is happening as the import is being done?

yes

@lisak - As mentioned in log can you enable debug logging in log4j.properties file and see the detailed root cause.

Also how many objects are available in your application package?

The package has 90 objects.

I don't see a log4j.properties file within the logs directory for Appian. Is this something I can just create and assign?

I have seen this error once before and it resurrected itself after shutting down Appian (per w/e your standard procedures are). Ensuring that the engines are all shut down and that the application server is shutdown and search server is shutdown. Restarting the machine (be it physical or virtual), and then starting the Appian Engines, search server, and application server back up. I would recommend trying that if it is not too painful to get the environment fully restarted. I know restarting is not the answer that anyone wants to hear, but it might be worth a shot.

You will find customizing log properties file - forum.appian.com/.../Customizing_Application_Logging.html

Another option is to try to restart the applications server and engines. It might resolve automatically.