Flow is not starting, no execution record

[Ron28]

I have an issue at the moment where a flow is not starting when triggered from the Service Catalog, and gives an "Internal Server Error" when running the flow via the "test" button. 

Background - I back up my app scope to Bitbucket, which I attempted to do a couple of days ago but this didn't work and I had an error saying something to the effect that files in the repository had not been applied to the code in the ServiceNow instance.  I found an article from ServiceNow where it suggested to stash my changes, then re-apply the stash. I did exactly that but ever since, I am unable to start my flow. 

In Flow Designer, there are no execution records for the flow. When I use the Service Catalog to trigger the flow, I just see an "error" in the flow execution tab. When triggering the flow from the "test' button and entering a Requested Item record, I just get an "internal server error". The error in the flow execution tab shows a link to the context record which has an error but other than something has a null value where it shouldn't, I can't work out what the issue is from that. 
Searching the node logs I do see an error relating to an execution plan but I didn't create one before so don't understand why the error.

I installed the code from the repository onto another ServiceNow instance where I get the same error. 

Any suggestions?

Thanks
Ron

[Ankur Bawiskar · Accepted solution]

@Ron28 

Did you try to create flow again from scratch and set trigger as Service Catalog?

How are the catalog items submitted? Is it from user via UI or via script?

[Ron28]

Hi Ankur

It would seem that in the process of creating the local stash then re-applying it after getting a copy of the repository didn't apply a number of the Service Catalog Item variable changes correctly.  This meant that the main flow couldn't be activated as the errors were in subflows, not in the main flow. The main flow could be saved and activated without it giving any errors, however the "activate" button remained active and if you looked next to the Flow title, it still showed "inactive". 
We ended up copying the flows then modifying them which was a lengthy process due to the complexity of the application, but we got there. All subflows were updated, checked and published as well as the main flow properly activated. 
Essentially your suggestion would have worked - create the flow from scratch - I'll mark your asker as correct.

Lesson learned here, back up more frequently with a smaller number of updates each time.