#442 [Feature] Resource Manager should trigger Exponential backoff for lack of resources Issue created by EngHabu Motivation: Why do you think this is important? When Resource Manager.AllocateToken() fails (due to lack of resources), propeller will keep traversing the same workflow over and over again attempting to allocate token and wasting time/resources. Goal: What should the final outcome look like, ideally? When AllocateToken fails, it should trigger exponential backoff and hold off attempting to allocate tokens to relieve pressure on the workers. Flyte component ☐ Overall ☐ Flyte Setup and Installation scripts ☐ Flyte Documentation ☐ Flyte communication (slack/email etc) ☑︎ FlytePropeller ☐ FlyteIDL (Flyte specification language) ☐ Flytekit (Python SDK) ☐ FlyteAdmin (Control Plane service) ☑︎ FlytePlugins ☐ DataCatalog ☐ FlyteStdlib (common libraries) ☐ FlyteConsole (UI) ☐ Other flyteorg/flyte

#442 [Feature] Resource Manager should trigger Exponential backoff for lack of resources Issue closed as not planned by github-actions[bot] flyteorg/flyte