Jump to content

Rique

Member
  • Content Count

    4
  • Joined

  • Last visited

  1. Martien, the errors seem to have been largely eliminated. I was able to get it to throw an error by mixing the order of things up (putting priority after the task, then label, then time for example) - but if I am disciplined in how I enter the order of things, I don't get errors anymore. I still cannot, however, get labels or priority to work. There are no error messages, there is no indication of poor syntax or anything like that, it's just that those values are not captured by Todoist. I've even tried entering just a task name, followed by priority (or followed by a label) - still no joy. Task name, time assigned and project assigned all work consistently well - so changing the names has helped a bit. But I'm not "there" yet with regards to priority or label. Priority is not that big a deal (I use it rarely), but labels are. Given Martien is otherwise occupied with the important task of parenting, is there anyone out there who can perhaps help with this? Please? Thanks! Rique
  2. Martien, First of all - congratulations! I hope you are getting some sleep. Often, that's a problem. Secondly - I will try your suggestion. I've just torn my Todoist setup down recently and am starting anew with a very different configuration than I'd used before. The timing is good to rename things. I will check back in and report my results. Thanks! Rique
  3. Using Brewdoctor, I was able to make improvements. However, I still get the occasional error and cannot get labels or priority to work at all. Would anyone have any idea of what I should check next? Martien?
  4. Hello Martien, I am having an issue with this workflow. I have installed Brew, have installed node.js, fixed an issue with the symlinks (all seems well with node now), the node -v command returns a "7.4" string - so all is well, correct? Not quite... for any feature which requires node, I get an error or a failure (without an error). For example, when I use this syntax with Alfred (todo my task, tomorrow @ 9, Single actions - {with Single actions signifying the Project} ), I get an error - and the task is not entered. If I stay away from project entry and only try to use a label (@my_label), the task enters just fine in the Inbox (as expected), but the label is not added. Here's the debug log: [2017-01-29 01:27:42][input.keyword] Processing output of 'action.script' with arg 'walk the dog, tomorrow @ 7, Single actions' [2017-01-29 01:27:45][ERROR: action.script] % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 545 100 263 100 282 557 597 --:--:-- --:--:-- --:--:-- 598 [2017-01-29 01:27:45][action.script] Processing output of 'utility.junction' with arg 'Error: Invalid temporary id","command_type":"item_add","error_code":16,"http_code":400}},"temp_id_mapping":{},"seq_no' [2017-01-29 01:27:45][utility.junction] Processing output of 'utility.filter' with arg 'Error: Invalid temporary id","command_type":"item_add","error_code":16,"http_code":400}},"temp_id_mapping":{},"seq_no' [2017-01-29 01:27:45][utility.filter] Processing output of 'output.notification' with arg 'Error: Invalid temporary id","command_type":"item_add","error_code":16,"http_code":400}},"temp_id_mapping":{},"seq_no' [2017-01-29 01:27:45][utility.junction] Processing output of 'utility.filter' with arg 'Error: Invalid temporary id","command_type":"item_add","error_code":16,"http_code":400}},"temp_id_mapping":{},"seq_no' Could the issues I am having be somehow related to node.js? All seems to be well with it (judging from the output from node -v). Is it possible the workflow is not fully compatible with the latest update to MacOS Sierra (I am running 10.12.3)? Can you please advise? I like this workflow very much, however - sadly - I cannot take advantage of the inclusion of Projects or labels. Please and thanks! Best, Rique
×
×
  • Create New...