Anyone seen this before on a resume of the megates...
# aws-megatests
j
Anyone seen this before on a resume of the megatests? `
r
oh no, I think that is from me messing around with setting default queues and having on demand fallbacks
🚫 2
ohno2 1
j
Can I do anything about it? 😬
r
can you link me the run. And yes, but I need to find a better way then in general
m
I think I have seen it too
Wanted to check with Rike about it, but forgot
r
Fix here:
Copy code
process {
    queue = { task.attempt > 1 ? 'TowerForge-6nSba1hDuNFP08JP7SjigJ' : 'TowerForge-5xrh62dl82REkzWq5o4Sd7-work' }
}
a bit weird that it occurs when it does and only sometimes
j
Shall I add it to the custom config block?
meow yes 1
r
I'll probably don't have time to look into this this week and I have people visiting over easter. Maybe I can play around with it on Friday
j
(if I resume again)
j
That seemed to work! Now it's my problem 😉
r
this is fixed now. Sorry about that
❤️ 1