Rank 2: Process
You can see the image, "Build archive was not created", even though build ran fine
Votes
0
Replies
8
Participants
3
Messages
9
Rank 2: Process
You can see the image, "Build archive was not created", even though build ran fine
Rank 2: Process
Hey @Tessa, here is the thread
@Meldiron can you take a look at this and see if it's something on our end or something?
heyy @SahilG 👋 Most commonly I see this error coupled with crash, and exit code hinting over-usage of memory.
Let's try that, as initial solution. Please try to increase specs in settings to highest memory, and redpeloy. See if that works. If yes, you can try to pin-point which specs is enough, while still costing as little as possible
(dont worry, only 1 build will be charged at max specs, so usage should be barely affected)
Rank 2: Process
But I am on free plan 😅
Interestiiing 🤔 Ill see if raising limits could make sense.
Out of curiousity, would you say your website is small / medium / large?
Rank 2: Process
the codebase size is around 2mb and with public assets it extends to 7mb. so you can say small-medium
I will be making quick patch to enforce slightly higher memory limit for builds, until we get better understanding of how we want to solve this long-term.
This is good news for you - builds will start to work, and you can remain on free plan.