Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
Instead of updating both dictionaries in parallel, update them sequentially with a small delay.
Why?
There's been a few reports now of opt in and out links 404ing, I've traced the issue to an issue with edge dictionary updates reflecting in fastly's VCL.
The edge dictionaries are updated successfully according to the API and the GUI. But it isn't reflected in the VCL.
I suspect this could be a bug in Fastly's API with updating multiple dictionaries simultaneously.Fastly reccomend avoiding concurrent requests! See belowTo confirm/mitigate, I suspect giving a few milliseconds between the API calls will help.
There's also a note on this docs page about avoiding concurrent updates https://www.fastly.com/documentation/reference/api/#rate-limiting
Screenshots
The Dictionary GUI is always updated with changes as expected

But this is not always reflecting in the "Complete VCL"