#3357 [UI Feature] UX improvement when running out of project quota Issue created by pradithya Motivation: Why do you think this is important? Flyte provides the capability to enforce CPU and Memory quota per project. We use this feature to avoid one project from consuming shared K8S cluster resources. As the size of the workflow is getting larger, the quota limit per project is getting hit quite often which delays the workflow execution. Currently, there are several UX areas that could be improved to handle the project quota. 1. When a task is scheduled but the host project is running out of quota, the timeline page still shows the task state as running. Ideally, the running state is only entered when there is a pod executing the task. 2. There should be a way to inform users that their workflow execution is affected by project quota. As of now, we can only see this information in the flyte propeller's log

Failed to launch job, resource quota exceeded. err: [BackOffError] The operation was attempted but failed, caused by: pods "fec52e914a8c0b0b7000-n3-0" is forbidden: exceeded quota: project-quota, requested: limits.memory=64Gi, used: limits.memory=192Gi, limited: limits.memory=200Gi

Goal: What should the final outcome look like, ideally? • Users should be able to identify quickly if their workflow execution is affected by project quota. • Transition to "RUNNING" state should be accurate Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte