error - "This item has exceeded the maximum number of revisions"

Comments

14 comments

  • Domenico Matteo

    Hi Lada,

    I'm sorry to say that there is nothing we can do about it at the moment.
    The number of revisions per item is limited to 5000, and we have no way of removing old revisions yet.
    The limit exists to ensure that automated synchronisations don't go crazy and fill our database with revisions. 

    I've filed an internal product input to rotate revisions, so that when number 5001 comes in, number 1 goes out, etc etc.

    In the meantime the only thing I can suggest you is to clone the item (e.g. PodioItem::Duplicate) and update items via the API as a result of an actual change, not via automated time interval.
    The cloned item will not have the inbound relationships of it's original, but will have the correct outbound relationships (if any).

    Hope this helps.

    Best,
    Domenico

    0
    Comment actions Permalink
  • Ladislav Soukup

    Hi Domenico,

    thanks for reply :) Problem is, that the value is Youtube subscribers, Instagram Followers, etc... so it is changing almost each and every hour... I have set longer update interval, but in ideal world, we would like to have it updated on hourly basis...

    The second catch is, that if I duplicate the object, it will break the relation to other objects in podio :( So the only "rescue" is the update on your backend or some kind of API to scratch old revisions (or a way to turn it off as in this specific case I don't need the history)

     

    Looking forward for future updates :D

    0
    Comment actions Permalink
  • Rainer Grabowski

    Hi Domenico,

    is there any progress on this? 

    "I've filed an internal product input to rotate revisions, so that when number 5001 comes in, number 1 goes out, etc etc."

    Or is 5,000 still the limit?

    Rainer

    1
    Comment actions Permalink
  • Guido Sondern

    +1

    0
    Comment actions Permalink
  • Domenico Matteo

    Hi Rainer,

    there is no consensus in the team that the revision rotation will benefit Podio as a whole, therefore we'r not moving forward with it.
    5000 revisions is, and will remain, the limit.

    The idea of exposing a way of removing old revisions though is currently under evaluation

    Thanks,
    Domenico

    0
    Comment actions Permalink
  • Rainer Grabowski

    Thanks, Domenico.

    What exactly is counted as a revision? Are changes in a calculation field also counted as revisions? If multiple fields are updated at the same time (e.g. by a flow) - is that counted as 1 revision or as multiple? 

    Rainer

    0
    Comment actions Permalink
  • Domenico Matteo

    Things that counts as one revision (possibly non exhaustive)

    • Change to any number of values in a single call
      e.g. {"money":{"currency":"USD","value":"1000"}, "number": "99"} and {"number": "99"} both count as one
    • Workflows that changes any number of fields

    This that do no count as revisions (definitely non exhaustive)

    • calculation fields
    • changes to app template (including field configs, help text, labels, etc...)
    • adding/changing/deleting comments
    1
    Comment actions Permalink
  • Rainer Grabowski

    Hi Domenico, thanks for the clarification!

    0
    Comment actions Permalink
  • Rudolph de Kock

    I have the same problem , my only problem is that I can't clone the item , because I have 4871 inbound relationships to this item. :(

    Hope this gets fixed soon...

    2
    Comment actions Permalink
  • Connie Illingworth

    I am getting the error logged in Globiflow from a flow that updates and item in our video library. I can't believe we could have made 5000 revisions to any one item in our training video library. With that said, I do have a central staff reference app used all over Podio. Are each item referenced to a single item in the reference app counted as a revision? (Let me know if I'm not making sense and I'll try to explain better.)

     

    0
    Comment actions Permalink
  • Chris Blanchard

    A straightforward concept (perhaps not necessarily a simple implementation) would be what SharePoint has done for a decade now, which is to allow the user the opportunity to configure a maximum number of revisions or versions of items in an app (in addition to the initial creation event revision).

    It would seem advantageous to have a process whereby old revisions are discarded automatically on Podio's back-end according to the user's configured settings in the app.  Allowing users to throttle the number of maintained revisions down from 5000 would allow Podio to keep the back-end DB cleaner.

    I could see throttling most of our hundreds of apps down to just a reasonable hand full of revisions per item (like <100). 

    1
    Comment actions Permalink
  • Carson Young - Red Cliff Labs

    Hi Domenico (Podio Team)

    I appreciate the transparent feedback here from early 2017:

    "there is no consensus in the team that the revision rotation will benefit Podio as a whole, therefore we'r not moving forward with it.
    5000 revisions is, and will remain, the limit.

    The idea of exposing a way of removing old revisions though is currently under evaluation

    Thanks,
    Domenico"


    Is there any update on the potential idea for exposing a way to remove old revisions? 

    As we move into 2019 the user base and demand of Podio Systems is far greater than in the past. Would love to see a solution here for the power users.

    I hate seeing clients that have a solid Podio system and enjoy using it, but then have to start at ground zero because they outgrow Podio based on situations like this.

    0
    Comment actions Permalink
  • Sara Høeg Højlund-Rasmussen

    Hi Carson,

    No update yet, we'll make sure to keep this thread updated if we have news to share in the future.

    //Sara - Podio

    0
    Comment actions Permalink
  • Craig de Kock

    Is there a way for us to cleanup some of the revisions to buy back some space here maybe and help this within the limit without coding something?

    1
    Comment actions Permalink

Please sign in to leave a comment.

Powered by Zendesk