Metadata Modified Date Updated on Failure

Issue #1153 resolved
Tyler Mowbrey created an issue

Hello,

Today when trying to deploy reports I used the "Deploy Modified Metadata" option with an option of "Context" with all reports and report folders selected (~2400 reports). Upon completion, a failure was encountered. I went and remediated the failure in about 21 reports and then went back and used "Deploy Modified Metadata". At this point, Illuminated Cloud only found 21 changes to deploy.

I'm wondering if the internal modified date or the comparison date is not being changed back in the event of a failure.

Comments (8)

  1. Tyler Mowbrey reporter

    Hi Scott,

    I attached the logs, not sure which is applicable. I did the following:

    1. Deploy Modified Metadata - 7 Files pending - Failed
    2. Manually edited metadata for 1 file
    3. Deploy Modified Metadata - 8 Files Pending - Failed
    4. Deploy Modified Metadata - 7 Files Pending - Failed (This was interesting as it didn't include the initial file I changed in step 2)
    5. Manually edited metadata for same 1 file
    6. Deploy Modified Metadata - 8 Files Pending - Failed
    7. Deploy Modified Metadata - 7 Files Pending - Failed (This was interesting as it didn't include the initial file I changed in step 2 and 5)

    Hopefully this helps. Let me know if you'd like me to try reproducing again without the initial 7 failures.

    Tyler

  2. Scott Wells repo owner

    Thanks, Tyler. I'll likely review it tomorrow. I'll let you know what I find and/or if I need more logs from you (doesn't seem like I should, though).

  3. Tyler Mowbrey reporter

    Thanks Scott! No hurry on my end, was easy to move forward with what I needed to do.

    Thank you very much for the quick response and help!

    Tyler

    (PS. Was watching your play by play today for a second time, it is quite brilliant!)

  4. Scott Wells repo owner

    Ah, cool on the Play by Play! That was a really great experience. Don is truly amazing!

  5. Scott Wells repo owner

    I found and fixed what is likely (hopefully?!) the underlying issue here. It was included in one of the last 2-3 releases. Resolving this for now but if you find that the behavior still exists, please let me know.

  6. Log in to comment