►
From YouTube: Digital Experience Retro - May 18, 2023
A
C
Yeah
I
just
I've
seen
so
many
of
these
case
study
Mrs
come
through
and
I
think
we've
been
doing
an
extremely
good
job
on
it.
I've
noticed
that
they've
been
piling
up
and
poor
Chandler
has
like
a
backlog,
I
think
of
like
20
case
studies
to
review
so
just
good
job.
Everyone
I've
seen
Mrs
from
like
everybody
on
the
case
study
so
yeah,
just
as
for
once
we're
like
too
fast
but
yeah.
D
Oh
yeah
I
just
wanted
it
on
the
record,
because
I
know
we
just
briefly
talked
about
it
before
we
hit
record
but
just
want
to
say
great
job
to
Trevor
and
Mateo
on
the
AI
page.
It
looks
fantastic.
We
got
a
great
shout
out
from
Ashley
this
morning
on
it,
but
yeah,
and
it
was
a
very
quick
turnaround
too
I.
Don't
think
people
like
understand
like
it
was.
We
got
the
content
very
quick.
Everything
moved
really
fast,
so
to
deliver
that
and
get
that
onto
the
website.
So
quick
was
amazing.
E
E
Obviously,
I
went
through
and
compressed
about
31
images
that
saved
us
59
Megs,
which
is
too
much
for
that
number
of
images.
So
it's
something
that,
right
after
we
push
that
up,
we
got
a
note
from
Hannah
about,
like
summer
pages,
are
enormous
future
file
sizes
we'd
already
addressed
most
of
these,
but
it's
something
that
it's
going
to
keep
coming
up
and
it's
something
that,
as
we
like
this
quarter,
it's
for
a
lot
of
people's
accounts
like
mobile,
optimization
and
like
six
Meg
files
and
great
for
mobile
data.
E
C
Yeah
I,
don't
normally
know
to
fix
for
this,
but
we've
had
this
kind
of
ongoing
thing
for
I.
Don't
know
how
long
now
it
it
kind
of
stopped
happening,
but
essentially
the
the
www
repository
tries
to
fetch
the
artifacts
from
the
buyer,
experience
build
and
deploy
and
for
some
reason
there
were
four
four
and
again
it
happened
like
a
weird
time.
This
week
it
was
like
I,
don't
know
if
it
was
like
a
Tuesday
or
something
Monday.
C
So
the
Quick
Fix
is
just
push
another
Mr
and
it'll
upload
the
artifacts,
the
artifact
timeout's
a
week.
We
push
stuff
like
every
day,
I'm,
not
too
sure
where
they're
coming
from,
but
maybe
just
something
we
can
keep
an
eye
out
and
try
and
see
why
this
is
happening.
I
wish,
we
knew
why
artifacts
would
disappear.
There
was
a
couple
incidents
I
think
this
week
with
GitHub.
So
maybe
that
was
the
cause,
but
yeah
I
guess
just
something
to
keep
an
eye
out
for
not
necessarily
to
improve
on.
A
I
didn't
yeah
I
didn't
write
this,
but
maybe
somewhere
in
our
handbook
we
could
put
kind
of
a
playbook
for
troubleshooting
that,
like
I,
know
to
add
a
period
somewhere
and
try
to
push
up
a
new
artifact.
You
know
this,
but,
like
you
know,
we
could
write
that
somewhere
so
that
anyone
who
runs
into
it
can
can
do
that.
A
A
E
C
Yeah
it's
funny
because
we
have
a
setting
where
it
says
that's
kind
of
Lauren
mentions
like
we
have
a
rule
that
says:
if
the
pipeline
fails,
don't
touch
the
artifacts,
but
maybe
that's
not
working.
That
setting
is
not
working,
so
it
should
in
the
documentation.
It
says
it
uses
the
last
successful
job.
So
you'd
think
that
it
would,
but
maybe
we
you're
right
at
something
and
that's
just
like
build
it
again
like
if
it
fails
because
of
this
because
at
404
is
like
we
could
parse
that
response,
maybe.
E
F
C
If
it
has
an
interim,
we
could
change
that
I
think
the
only
job
that
fails
is
the
404
one.
We
can
change
that
to
a
warning
again.
It
doesn't
really
matter.
It
doesn't
go
through
the
whole
pipe
process
anyway,
like
it
just
builds,
it
doesn't
really
do
anything,
but
just
to
kind
of
rule
out
something.