@anshul96go Just to give you more context: when you submit a strategy to the contest, the strategy is queued. Depending on the current load, the processing can take some time. If you submit when many other users are submitting, then processing will take more time.
Moreover, when you develop on the notebook, processing is instantaneous because no particular checks are done (well, it depends on the complexity of the strategy). You just run your code and get the result.
If you code it using a single-pass approach the processing will be very fast. If you use our backtesting function (which prevents forward looking), processing will be a bit slower.
When you submit the strategy, however, several sanity checks are run on the strategy. The system checks if allocations are defined for all datapoints, if your strategy is performing looking forward operations, if it stops producing the output before current day, it computes the Sharpe ratio and other statistical indicators, and moreover it computes the correlation of your strategy with all examples we provide, as we do not allow an example to win a contest...so the processing is slower.
For quick development, please refer to the results you get in the notebook, submit the strategy and then it will be ok.