Hi @kapa.ai < After failing to upgrade to 1.8.5, I tried reverting to 1.1.0 I get the below error. probably data is corrupted. can i delete a specific entry from table to fix the issue. could you help? 2026-03-03 062107 ERROR i.a.b.Application(main):25 - Unable to bootstrap Airbyte environment. java.lang.RuntimeException: com.fasterxml.jackson.core.JsonParseException: Invalid numeric value: Leading zeroes not allowed at [Source: REDACTED (

StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION

disabled); line: 1, column: 2] at io.airbyte.commons.json.Jsons.deserialize(Jsons.java:101) ~[io.airbyte-airbyte-commons-1.1.0.jar:?] at io.airbyte.data.services.impls.jooq.DbConverter.buildStandardWorkspace(DbConverter.java:184) ~[io.airbyte-airbyte-data-1.1.0.jar:?] at java.base/java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:197) ~[?:?] at java.base/java.util.ArrayList$Itr.forEachRemaining(ArrayList.java:1085) ~[?:?] at java.base/java.util.Spliterators$IteratorSpliterator.forEachRemaining(Spliterators.java:1939) ~[?:?] at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:509) ~[?:?] at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499) ~[?:?] at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:575) ~[?:?] at java.base/java.util.stream.AbstractPipeline.evaluateToArrayNode(AbstractPipeline.java:260) ~[?:?] at java.base/java.util.stream.ReferencePipeline.toArray(ReferencePipeline.java:616) ~[?:?] at java.base/java.util.stream.ReferencePipeline.toArray(ReferencePipeline.java:622) ~[?:?] at java.base/java.util.stream.ReferencePipeline.toList(ReferencePipeline.java:627) ~[?:?] at io.airbyte.data.services.impls.jooq.WorkspaceServiceJooqImpl.listStandardWorkspaces(WorkspaceServiceJooqImpl.java:161) ~[io.airbyte-airbyte-data-1.1.0.jar:?] at io.airbyte.config.persistence.ConfigRepository.listStandardWorkspaces(ConfigRepository.java:232) ~[io.airbyte.airbyte-config-config-persistence-1.1.0.jar:?] at io.airbyte.bootloader.Bootloader.createWorkspaceIfNoneExists(Bootloader.java:199) ~[io.airbyte-airbyte-bootloader-1.1.0.jar:?] at io.airbyte.bootloader.Bootloader.load(Bootloader.java:116) ~[io.airbyte-airbyte-bootloader-1.1.0.jar:?] at io.airbyte.bootloader.Application.main(Application.java:22) [io.airbyte-airbyte-bootloader-1.1.0.jar:?] Caused by: com.fasterxml.jackson.core.JsonParseException: Invalid numeric value: Leading zeroes not allowed at [Source: REDACTED (

StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION

disabled); line: 1, column: 2] at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:2572) ~[jackson-core-2.17.2.jar:2.17.2] at com.fasterxml.jackson.core.JsonParser._constructReadException(JsonParser.java:2598) ~[jackson-core-2.17.2.jar:2.17.2] at com.fasterxml.jackson.core.base.ParserMinimalBase.reportInvalidNumber(ParserMinimalBase.java:599) ~[jackson-core-2.17.2.jar:2.17.2] at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._verifyNLZ2(ReaderBasedJsonParser.java:1706) ~[jackson-core-2.17.2.jar:2.17.2] at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._verifyNoLeadingZeroes(ReaderBasedJsonParser.java:1693) ~[jackson-core-2.17.2.jar:2.17.2] at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._parseNumber2(ReaderBasedJsonParser.java:1555) ~[jackson-core-2.17.2.jar:2.17.2] at com.fasterxml.jackson.core.json.ReaderBasedJsonParser._parseUnsignedNumber(ReaderBasedJsonParser.java:1364) ~[jackson-core-2.17.2.jar:2.17.2] at com.fasterxml.jackson.core.json.ReaderBasedJsonParser.nextToken(ReaderBasedJsonParser.java:777) ~[jackson-core-2.17.2.jar:2.17.2] at com.fasterxml.jackson.databind.ObjectMapper._initForReading(ObjectMapper.java:4992) ~[jackson-databind-2.17.2.jar:2.17.2] at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4898) ~[jackson-databind-2.17.2.jar:2.17.2] at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3848) ~[jackson-databind-2.17.2.jar:2.17.2] at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:3816) ~[jackson-databind-2.17.2.jar:2.17.2] at io.airbyte.commons.json.Jsons.deserialize(Jsons.java:99) ~[io.airbyte-airbyte-commons-1.1.0.jar:?] ... 16 more

You’re hitting the same class of error that’s been reported when bootloader tries to read workspace data and Jackson fails on malformed JSON / numeric values. The knowledge sources confirm this pattern but do not document a safe, supported way to “just delete one row” to fix it. [Failed deploy 1.6.1; Could not deploy 1.6.0] A few important points from the available information: • The error occurs while listing workspaces (

WorkspaceServiceJooqImpl.listStandardWorkspaces

), so the bad data is almost certainly in the

workspace

-related configuration in the Airbyte DB, not in a connector/job table. [Failed deploy 1.6.1] • In a similar upgrade/migration situation, a user tried deleting a row (in their case from the

dataplane

table) and it only led to more “database cannot be accessed” / column‑mismatch errors; they ultimately had to restore the database to its pre‑upgrade state. [Helm 1.8.0 missing webapp] • Another thread with a JSON parsing / numeric error during upgrade also ended up being a migration/state issue rather than something fixed by a single-row delete. [Error upgrading 0.40.17→0.50.1] Because of that, and based strictly on the docs you provided: 1. I cannot safely recommend deleting a specific entry in any table as a fix. The knowledge sources explicitly show that ad‑hoc deletes can leave the schema and data out of sync and force a full DB restore. [Helm 1.8.0 missing webapp] 2. The only clearly successful recovery path documented is: ◦ Restore the Airbyte database from a backup taken before the failed upgrade attempt. [Helm 1.8.0 missing webapp] ◦ Then re‑attempt the upgrade following the supported path and version steps. 3. If you don’t have a usable backup, the knowledge sources do not provide a supported, step‑by‑step procedure to: ◦ Identify exactly which workspace row is malformed, or ◦ Edit or delete it in a way that’s guaranteed not to break other parts of Airbyte. Given these limits, the safest actions, based on the available information, are: • Restore the DB to a known‑good state from before the 1.8.5 upgrade attempt, then bring Airbyte back up on 1.1.0 using that DB. [Helm 1.8.0 missing webapp] • If you have Airbyte Enterprise / support, open a ticket and share these bootloader logs so they can guide you on any targeted DB edits. • If you’re OSS only, I’d suggest posting this full stack trace and your version path on the Airbyte forum or in the GitHub issues, referencing the existing “Invalid numeric value: Leading zeroes not allowed” reports, so the team can advise on a migration fix. [Could not deploy 1.6.0; Failed deploy 1.6.1] I’m sorry I can’t give you a precise “delete row X from table Y” answer—there’s simply no such guidance in the sources, and the one example of manual deletion led to more corruption, not a fix. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.