Closed timoerlemans closed 5 years ago
Strange. I can't really imagine why the job would fail. Can you access your database?
Yes, I can.
OK good. Find the table 'imports' and locate the entry with key
It should have a field configuration with some JSON in it. Could you run it through jsonlint, remove private data if necessary and share it?
Here is the field configuration (the JSON is valid according to jsonlint):
{
"access_token": "hidden",
"access_token_expires": 1546974658,
"budgets": [
{ "id": "57d46822-dd62-4fdb-bbeb-488af99614a7", "name": "hidden", "currency_code": "EUR" },
{ "id": "f104fe2a-20c2-4deb-92af-b9248169cbee", "name": "hidden", "currency_code": "EUR" }
],
"selected_budget": "f104fe2a-20c2-4deb-92af-b9248169cbee",
"accounts": [
{
"id": "ee992a8e-714a-4a46-b4ff-014b12902141",
"name": "hidden",
"type": "checking",
"on_budget": true,
"closed": false,
"note": null,
"balance": 0,
"cleared_balance": 0,
"uncleared_balance": 0,
"transfer_payee_id": "d8662a6e-f196-4d70-a26c-04f51ff9c217",
"deleted": false
},
{
"id": "756c8c70-6560-467e-b521-0fb296cfb51d",
"name": "hidden",
"type": "savings",
"on_budget": true,
"closed": false,
"note": null,
"balance": 0,
"cleared_balance": 0,
"uncleared_balance": 0,
"transfer_payee_id": "4be9c4bf-2c9f-4b35-b5c8-d297356be2ba",
"deleted": false
},
{
"id": "8f346973-3a19-43b5-972c-20615ec304fe",
"name": "hidden",
"type": "otherLiability",
"on_budget": false,
"closed": false,
"note": null,
"balance": 0,
"cleared_balance": 0,
"uncleared_balance": 0,
"transfer_payee_id": "f09dc1c2-f9e2-4624-99e6-f2cb6d773698",
"deleted": false
},
{
"id": "92dfc386-f961-4dfe-a6ef-7fd81aab13a6",
"name": "hidden",
"type": "savings",
"on_budget": true,
"closed": false,
"note": null,
"balance": 0,
"cleared_balance": 0,
"uncleared_balance": 0,
"transfer_payee_id": "22011ca1-4254-4998-b4a8-867f34f4d152",
"deleted": false
}
],
"mapping": {
"ee992a8e-714a-4a46-b4ff-014b12902141": 78,
"756c8c70-6560-467e-b521-0fb296cfb51d": 0,
"8f346973-3a19-43b5-972c-20615ec304fe": 0,
"92dfc386-f961-4dfe-a6ef-7fd81aab13a6": 0
},
"apply-rules": true
}
I think I found the issue, but I can't confirm it. I assume you have four accounts at YNAB, and linked only one to Firefly III? So only for one account, you selected an asset account to import into?
In this case I did, yes. But it doesn't matter if I link the other ones as well, I still get the same error. (Except for the otherLiability one, because that's not an account but a Liability)
Is the number also 0 3x for the configuration of those new import jobs?
Sorry, should have mentioned that I changed those numbers to 0 for privacy reasons.
Alright, so in this part specifically:
"mapping": {
"ee992a8e-714a-4a46-b4ff-014b12902141": x,
"756c8c70-6560-467e-b521-0fb296cfb51d": x,
"8f346973-3a19-43b5-972c-20615ec304fe": x,
"92dfc386-f961-4dfe-a6ef-7fd81aab13a6": x
},
The x
's are in fact filled with numbers, and these numbers are not 0?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
I had this issue and found that it would error unless I assigned an account for everything to be imported into (do not import didn't work)
Thanks for the feedback. I'll check it out!
I am running Firefly III version 4.7.9
Description I'm trying to import You Need A Budget into Firefly III. I did all the necessary work (secret ID etc.) and I'm able to select a budget (I have 2 budgets in YNAB) and I can assign my YNAB accounts to my Firefly III accounts. After this, it starts importing (and it does import some things like expenses and revenue accounts. But after a few seconds, it stops and gives this error:
Tried it with other budget and different assigned accounts (also removed the first bank account I created and made a new one), but nothing seems to fix it...
Steps to reproduce See above (if possible)
Extra info Please add extra info here, such as OS, browser, and the output from the
/debug
-page of your Firefly III installation (click the version at the bottom).I run the app on a (free) Heroku instance.
/debug info:
Log with error and stack trace: