It does not know when to throw an error

[aprilmintacpineda]

I have been working on a version of my app for a month now, I have migrations all the way from last month:

2021-05-14T12_51_36.677Z
2021-05-17T14_13_02.781Z
2021-05-20T10_11_53.254Z
2021-05-24T13_36_40.541Z
2021-05-30T10_37_23.525Z
2021-06-01T12_09_03.153Z

but when I was trying to deploy to production, for some reason, it only managed to apply 2021-05-14T12:51:36.677Z which when translated is 2021-05-14T12_51_36.677Z which was the first migration, the rest of the migrations won't even get applied which kind of fucked my production app -- a good thing no one's using it yet, otherwise, I'm fucked.

It doesn't matter how hard I try to run fauna-schema-migrate apply, it won't do anything

yarn run v1.22.10
$ /home/runner/work/my-app/my-app/node_modules/.bin/fauna-schema-migrate apply
Fauna Schema Migrate - 2.1.2
---------------------------------------
--- Starting subtask Retrieving current cloud migration state
--- Finished subtask Retrieved current migration state
--------- Current cloud migrations----------
    2021-03-28T10:48:52.250Z
    2021-04-17T02:03:19.186Z
    2021-04-17T09:15:39.642Z
    2021-05-02T03:43:07.746Z
    2021-05-03T09:25:29.544Z
    2021-05-11T11:00:49.014Z
    2021-05-11T11:29:36.699Z
    2021-05-11T12:20:53.249Z
--------- Current local migrations ----------
    2021-03-28T10:48:52.250Z
    2021-04-17T02:03:19.186Z
    2021-04-17T09:15:39.642Z
    2021-05-02T03:43:07.746Z
    2021-05-03T09:25:29.544Z
    2021-05-11T11:00:49.014Z
    2021-05-11T11:29:36.699Z
    2021-05-11T12:20:53.249Z
    2021-05-14T12:51:36.677Z
    2021-05-17T14:13:02.781Z
    2021-05-20T10:11:53.254Z
    2021-05-24T13:36:40.541Z
    2021-05-30T10:37:23.525Z
    2021-06-01T12:09:03.153Z
--------- Task ----------
    apply 1 migrations


--- Starting subtask [ DB: ROOT ] Generate migration code
--- Finished subtask [ DB: ROOT ] Generated migration code
--- Starting subtask [ DB: ROOT ] Applying migration
--- Finished subtask Done applying migrations
Done in 1.88s.

I'm running it from Github actions.

[aprilmintacpineda]

After manually adding them one by one, I found out the problem (or at least what I think is the problem), it encountered an index that already exists, and instead of throwing an error, it just ignored the rest and pretended they never existed 🤷🏻‍♂️