Stephen,
Issues like this are seen when:
1) You already have a working production server. A consultant was task to development on top of that production server. The consultant may have to import data from the production server into Eclipse Agentry editor. The newly imported definition from the production server will be developed (changes - delta) but during publishing a new modification/minor all the definition will have a new lastUpdate time stamp. Using this new data in the server will make all the clients download the definition from scratch.
This is what was seen before in test.
In essence with respect to time (T0 to Tn):
T0 -----------------------------------------------------------------> Tn
Old Editor --> Publish definition --> Agentry Production (Works)
But
Production Server --> Import the definition to Eclipse --> Develop --> Publish new prod definition -> Production (May have issues)
2) If your changes even if it is minor somewhat touch the screensets. For example, you somewhat touch a particular complex table. This complex table is used in multiple screens and rules. Then this means that all those screenset, screens, validation rules, update rules and others that uses those screens will be touched. I have seen this happen. Normally you do not want to touch complex tables - did you somewhat modify a complex table that is used everywhere?
Another thing you may consider:
1) We have develop more fixes (Reference: AG-27803 - tried getting fixes from older release to be merged to SMP 3.0) to the Editor publishing with respect to TimeStamp or lastUpdate. Last known fixes and merges and test where done in at least SMP 3.0 SP05. Make sure you are at least in that level. The testing was move to that version from our notes it stated either fix or not fix (a fix SP05 was given but the totality was not confirmed by customer). But the technique I specified above is one thing that I know that may have issues as the system on import may have to reset the time (related to AG-27803). You may state your version of the editor so I may know if AG-27803 exist past version SP05 if you have the same story as I have given in item 1 above.
2) For item 2 like a complextable modification used everywhere, this may be a tough one because if you study the definition against that complex table and it is used everywhere the time may change. Did you or did you not touch a complex table on your minor update?
Hope this helps.
Regards,
Mark Pe
SAP Platinum Support Engineer