Back home
Reference

InspireLog error codes

When something fails in the app, InspireLog says so in the conversation and offers a small Details link underneath. Tapping it shows a three-digit code like 014. This page is where that code becomes something you can act on.

Find your code below (or open inspirelog.io/errors#your-code directly). Codes are permanent: a number never changes meaning, and retired ones stay listed.

How to read a code

The first digit tells you roughly what broke:

0xx
Connection
1xx
Sign-in & session
2xx
Conversation & model
3xx
Voice & speech
4xx
Data, backup & export
5xx
Purchases & subscription
9xx
Unexpected

0xxConnection

010

No internet connection

What happened: Your phone isn't connected to the internet, so the request never left it.

What to try

  1. Check that Wi-Fi or mobile data is on, and that Airplane Mode is off.
  2. Open any website in Safari. If that fails too, the problem is the connection, not InspireLog.
  3. Once you're back online, send the message again — it wasn't lost, it just never left your phone.
011

Request timed out

What happened: The request left your phone, but no answer came back in time.

What to try

  1. Try again once. A single timeout is usually a slow connection, not a broken one.
  2. If it keeps happening, move to a stronger Wi-Fi or mobile signal and try again.
012

Couldn't reach InspireLog

What happened: Your phone is online, but InspireLog's servers didn't answer.

What to try

  1. Wait a couple of minutes and try again — this usually clears on its own.
  2. If it lasts longer than about fifteen minutes, we probably know, but do email support@inspirelog.io with the code so we can confirm.
013

Unreadable response

What happened: InspireLog answered, but the reply wasn't in a form the app could read.

What to try

  1. Try again once — an unreadable reply is almost always a one-off.
  2. If you see it repeatedly, update InspireLog from the App Store: an old app can misread a newer server.
014

Network error

What happened: The connection to InspireLog broke partway through.

What to try

  1. Check your connection and try again. This is what a dropped Wi-Fi or a tunnel on the train looks like.
  2. If you're on a VPN or a restricted network (school, office), try without it.

1xxSign-in & session

110

Session expired

What happened: Your sign-in session is no longer valid, so InspireLog's servers turned the request away.

What to try

  1. Open Settings in the app, sign out, then sign back in with your Apple ID.
  2. Your conversations and memories stay on your phone — signing out doesn't remove them.
111

Sign-in failed

What happened: InspireLog's servers couldn't verify your Apple ID sign-in.

What to try

  1. Try signing in again. If Apple asks for a passcode or Face ID, complete it.
  2. Make sure this iPhone is signed in to iCloud with the Apple ID you want to use (iPhone Settings → your name).
  3. If it still fails, email support@inspirelog.io with the code.
112

Not permitted

What happened: Your account isn't allowed to do what the app just asked for.

What to try

  1. This one is on us: your account isn't allowed to do what the app asked, and that's a server-side setting, not something on your phone.
  2. Email support@inspirelog.io with the code and what you were doing.
113

Apple sign-in didn't complete

What happened: Apple's sign-in didn't finish, so InspireLog never received your credentials.

What to try

  1. Try again — Apple's sign-in sheet sometimes closes before it finishes.
  2. Check that Sign in with Apple isn't restricted on this device (iPhone Settings → Screen Time → Content & Privacy Restrictions).
  3. If it keeps happening, restart the phone and try once more.
114

Couldn't save your session

What happened: You signed in, but the app couldn't store the session securely on this phone.

What to try

  1. Try signing in again. This means your phone's secure storage refused a write, which is rare and usually momentary.
  2. If it happens twice in a row, restart your phone.
  3. Still stuck? Email support@inspirelog.io with the code.

2xxConversation & model

210

Service busy

What happened: The model that writes InspireLog's replies is overloaded right now.

What to try

  1. This one is on us. The model behind InspireLog is busy; it clears on its own, usually within a few minutes.
  2. Your message is still in the thread — send it again when the app says it's ready.
211

Response took too long

What happened: The model started on a reply but didn't finish within the time limit.

What to try

  1. Try once more. Long, complicated messages take longer; splitting one into two often helps.
  2. If every message times out, the model is having a slow spell — give it ten minutes.
212

Model error

What happened: The model that writes InspireLog's replies returned an error instead of a reply.

What to try

  1. This one is on us: the model returned an error instead of a reply. It should clear on its own.
  2. Try again in a few minutes. If you still see 212 an hour later, email support@inspirelog.io.
213

Request rejected

What happened: InspireLog's servers rejected what the app sent, which usually means the app is out of date.

What to try

  1. Update InspireLog from the App Store. The server rejected the request, which almost always means the app is older than the server expects.
  2. If you're already on the latest version, email support@inspirelog.io with the code — that's a bug on our side.
214

Invalid signal

What happened: The app sent a background signal that InspireLog's servers didn't recognise.

What to try

  1. Update InspireLog from the App Store — a background signal the server didn't recognise usually means an old app.
  2. Nothing you typed was lost; this affects background check-ins, not your messages.
215

Request refused

What happened: InspireLog's servers refused the request without saying why.

What to try

  1. Try again once.
  2. If it repeats, update InspireLog from the App Store, then email support@inspirelog.io with the code if it still happens.

3xxVoice & speech

310

Voice unavailable

What happened: Voice calling isn't switched on for InspireLog's servers right now.

What to try

  1. This one is on us: voice calling is switched off on our side right now. Text works as usual.
  2. Try calling again later. If it's still off after a day, we'd like to know — support@inspirelog.io.
311

Voice connection failed

What happened: The call couldn't be connected to the voice service.

What to try

  1. Try the call again. Voice needs a steadier connection than text — Wi-Fi is more reliable than mobile data here.
  2. If you're on a VPN or a network that blocks calls (some offices and campuses do), try without it.
  3. If calls never connect, email support@inspirelog.io with the code.
312

Speech unavailable

No longer in use

What happened: Text-to-speech wasn't switched on for InspireLog's servers.

What to try

  1. This code is no longer in use. If you see it, you're on an old version of InspireLog — update from the App Store.
313

Speech service error

No longer in use

What happened: The text-to-speech service returned an error.

What to try

  1. This code is no longer in use. If you see it, you're on an old version of InspireLog — update from the App Store.
314

Speech error

No longer in use

What happened: InspireLog couldn't turn its reply into speech.

What to try

  1. This code is no longer in use. If you see it, you're on an old version of InspireLog — update from the App Store.
315

Voice bot unavailable

What happened: The voice service InspireLog calls into isn't configured right now.

What to try

  1. This one is on us: the service that handles calls isn't configured right now. Text works as usual.
  2. Try again later. If it's still down after a day, email support@inspirelog.io.
316

Voice ran out of capacity

What happened: The voice model hit its capacity limit mid-call, so InspireLog had to hang up.

What to try

  1. Give it a minute and call again. The voice model hit its capacity limit mid-call, which is why InspireLog hung up rather than going quiet.
  2. What you said on the call before the hang-up was kept.
  3. If it happens on every call, email support@inspirelog.io — that's a limit we need to raise.
317

Call dropped

What happened: The live connection behind the call was lost.

What to try

  1. Call again. The live connection dropped — the same thing that happens to a phone call in an elevator.
  2. Wi-Fi is more reliable than mobile data for calls; switching helps if it keeps happening.

4xxData, backup & export

410

Deletion failed

What happened: InspireLog's servers couldn't delete your data.

What to try

  1. Tap Retry. If the server still can't delete your data, the app lets you delete everything on this phone only, and we'll finish the server side.
  2. Email support@inspirelog.io with the code and we will confirm the server-side deletion by hand.
411

Invalid query

What happened: InspireLog's servers didn't understand a request the app made about your data.

What to try

  1. Update InspireLog from the App Store — the server didn't understand a request about your data, which usually means an old app.
  2. If you're already up to date, email support@inspirelog.io with the code.
412

Backup upload failed

What happened: Your backup was prepared, but it couldn't be uploaded to your cloud storage.

What to try

  1. Check your connection and try the backup again.
  2. Make sure iCloud Drive is on (iPhone Settings → your name → iCloud → iCloud Drive) and that InspireLog is allowed to use it.
413

Backup couldn't be retrieved

What happened: Your backup couldn't be found or downloaded from your cloud storage.

What to try

  1. Check your connection and try again.
  2. Make sure this iPhone is signed in to the same iCloud account the backup was made from.
  3. If there genuinely isn't a backup yet, make one from Settings → Backup first.
414

Cloud sign-in failed

What happened: Your cloud storage wouldn't let InspireLog in.

What to try

  1. Open iPhone Settings → your name and make sure iCloud is signed in and not asking you to verify anything.
  2. Then come back and try the backup or restore again.
415

Backup couldn't be read

What happened: The backup was found, but it couldn't be decrypted, verified, or read by this version of the app.

What to try

  1. If this is a restore, check the passphrase — a wrong passphrase looks exactly like a corrupted backup.
  2. If the backup was made by a newer InspireLog, update the app from the App Store and try again.
  3. If neither applies, the backup may be damaged. Email support@inspirelog.io with the code; don't delete the backup yet.
416

Cloud storage full

What happened: Your cloud storage has no room left for the backup.

What to try

  1. Free up space in iCloud: iPhone Settings → your name → iCloud → Manage Account Storage.
  2. Then try the backup again.
417

Backup failed on this phone

What happened: The backup or restore failed on this phone, before anything reached the cloud.

What to try

  1. Try again — this failed on your phone before anything was sent, so nothing partial exists in the cloud.
  2. If it happens twice, restart the phone and try once more.
  3. Still failing? Email support@inspirelog.io with the code.

5xxPurchases & subscription

510

Purchase didn't go through

What happened: The App Store didn't complete the purchase.

What to try

  1. Try the purchase again. If the App Store asked you to confirm and you cancelled, that's expected — nothing was charged.
  2. Check iPhone Settings → your name → Payment & Shipping, in case a payment method needs updating.
511

Purchase couldn't be verified

What happened: The App Store reported a purchase, but its receipt couldn't be verified.

What to try

  1. This one is on us to sort out: the App Store says you bought it, but we couldn't verify the receipt.
  2. Email support@inspirelog.io with the code and the Apple ID email you used; we'll restore your access by hand.
512

Subscription not available

What happened: The App Store didn't return InspireLog's subscription product.

What to try

  1. Wait a few minutes and open the subscription screen again — the App Store sometimes fails to return the product.
  2. If you're on a TestFlight build, this is expected: the subscription isn't available in that build.
513

Nothing to restore

What happened: The App Store found no active InspireLog subscription for this Apple ID.

What to try

  1. Make sure this iPhone is signed in to the App Store with the Apple ID you subscribed with (iPhone Settings → your name → Media & Purchases).
  2. Then tap Restore Purchases again.
  3. If you're sure you subscribed and it still says nothing to restore, email support@inspirelog.io with the code.
514

Restore failed

What happened: The App Store couldn't check your purchases.

What to try

  1. Check your connection and tap Restore Purchases again.
  2. If the App Store keeps failing, sign out of the App Store and back in (iPhone Settings → your name → Media & Purchases).
515

Premium required

What happened: This feature needs an active Premium subscription.

What to try

  1. This feature needs an active Premium subscription. You can subscribe from Settings in the app.
  2. If you already subscribed, tap Restore Purchases on the subscription screen.

9xxUnexpected

900

Unexpected error

What happened: Something went wrong on InspireLog's side.

What to try

  1. This one is on us. Something failed on our side; it usually clears on its own.
  2. Try again in a few minutes. If you're still seeing 900 after an hour, email support@inspirelog.io with the code and roughly when it started.
999

Unrecognized error

What happened: The app hit a failure it doesn't have a number for yet.

What to do

  1. We don't have a number for this one yet, so this page can't explain it — but the app can: under the 999, it shows an internal code (something like SOMETHING_NEW or NSURLErrorDomain(-1005)).
  2. Tap Copy code in the app and email it to support@inspirelog.io with what you were doing. That's enough for us to find it, and it earns the failure a real number.
Email support@inspirelog.io

Still stuck?

Email support@inspirelog.io with the code and what you were doing when it appeared. The code is the useful part — it turns "it said it couldn't reach me" into something we can look up in seconds.