For Tower API Devs: My Github token ran out, such that I hit the following error on API triggered workflow runs: 403: Unknown pipeline repository or missing credentials:
Are Github tokens required to run repos? I thought we’d just be limited to 60 request per hour without token?
In which case, does Tower switch to ‘no-token repo run’ when the current token is expired?
(I know this is a tricky edge case, but tower behaviour is crucial for me to know in this case, thanks a lot in advance!) 
Hi @Jakob_Zeitler,
Apologies for letting this post linger, just stumbled across it. Great question / feature request.
Currently public repos will work without GitHub tokens with the low rate limit as you say. However, if you add GitHub credentials it will try to use those for everything. If the credentials are invalid, you hit the error you saw as you say - even if the repo is public.
Whilst we could do this, I worry that it might cause more trouble. I could imagine the behaviour then becoming very confusing - one day everything works and the next some stuff starts breaking for no obvious reason. Worse would be if behaviour changed subtly somewhere, though I’m not sure I can think of any examples where that’d happen.
What I’d prefer is instead to capture the expiration of the token explicitly and raise this to the user. Then rather than having a somewhat obscure / misleading error about Unknown pipeline repositories we can explain exactly what has happened and link them to their Platform credentials page where they could either delete or update their GitHub token.
Would this be satisfactory for your use case? If so, please go ahead and post it as a feature request at https://feedback.seqera.io/ (or I can on your behalf).
Phil