Executing a SSIS package from stored procedure is timing out - stored-procedures

Question

I have a conundrum and I'm stumped and hoping y'all can help.
Here is my scenario: I am loading data into our database through a web interface. First, I upload the file to the SQL box, then I call the script which extracts and loads the data into SQL.
I recently changed this process so that now, instead of executing the package from within the web application, I am calling a stored procedure to execute the script.
Here is the core of my code:
CREATE PROCEDURE [dbo].[ExecuteSsisPackage]
#Package NVARCHAR(100),
AS
BEGIN
SET NOCOUNT ON;
DECLARE #executionID BIGINT
EXEC SSISDB.catalog.create_execution
#folder_name = 'Imports', -- nvarchar(128)
#project_name = 'DataImports, -- nvarchar(128)
#package_name = #Package, -- nvarchar(260)
#use32bitruntime = 1, -- bit
#execution_id = #executionID OUTPUT -- bigint
SELECT #executionId
EXEC [SSISDB].[catalog].[set_execution_parameter_value] #executionId, 50, N'SYNCHRONIZED', #parameter_value = 1 -- turn on synchronization
EXEC ssisdb.catalog.start_execution #executionID;
RETURN (#executionID)
END
Here is the odd part: when I run the stored procedure from management studio it executes fine. However, when I execute this from the web application it times out. But, if I turn OFF synchronization it executes just fine through the web app. The problem with disabling synchronization is that I need to pull some summary info off the data after it has been loaded.
I've even tried rolling my own 'synchronization' from a post I found:
DECLARE #status AS BIGINT = 1;
WHILE(#status = 1 OR #status = 2 OR #status = 5 OR #status= 8)
BEGIN
PRINT 'Status: ' + CAST(#status AS VARCHAR(10))
PRINT 'waiting 2 seconds for Package to finish'
WAITFOR DELAY '00:00:2';
SET #status = (SELECT [Status] FROM SSISDB.[catalog].[executions]
WHERE execution_id = #executionID);
END
PRINT 'Exit Status: ' + CAST(#status AS VARCHAR(10))
This also times out. I did some digging and found that when the SP is executing from the web (but not management studio) there is a lock: LCK_M_S and the wait_resource is: KEY: 9:72057594041532416 (d28bcaafb8df). Again, this only occurs when executing the SP from the web app.
Some more digging unearthed the culprit for the lock. It is the PK_Operations key of the SSISDB.internal.operations table. This is the conundrum. Any ideas why this occurs only through the web and when synchronized it turned on??