Michael Neale James Dumay and I discussed this a bit. I think the correct way to fix this issue is to modify creation slightly such that once it's determined that the repository connection information is correct and a job has been created, send the user to the activity page immediately (e.g. don't wait 10 seconds or for it to complete). Next, modify the activity page to be aware of and show some indication of indexing activity, with the special case that there are no jenkinsfiles discovered - maybe put a spinner in the 'no pipelines' dialog and have it say 'searching for pipelines' or something instead and take away the buttons (there should be a little bit of design work on this). Finally, when indexing completes, refresh the activity page's data and if there aren't any pipelines, send the user to the pipeline editor as it does from creation now. This should solve a handful of usability issues around creation that have to do with indexing taking a while and/or activity page not refreshing.