Greg Diamond

Photographer Extraordinaire & Friend

[Greg Diamond @grgdmnd]

@AdobeCare @Greg @AdobeCare It seems like the conversation has stopped. Silence on Ticket LRD-422-3405 feels like a signal that you’ve given up on Case ADB-42703790-V3Q1.
I’m still here, still blocked, and still waiting for the Sync Engineer.
How do we restart this before Day 60 arrives?

[Greg Diamond @grgdmnd]

@thsottiaux It seems like if one’s dot invokes codex, it costs usage. And to get work done it seems like one’s dot needs to invoke codex. So… how…?

[Greg Diamond @grgdmnd]

@AdobeCare It seems like the server is restoring errors faster than my client can clear them. How can I be expected to resolve a queue that grows while I'm doing nothing? This requires a look under the hood by Sync Engineering.
Eng: LRD-422-3405
Case: ADB-42703790-V3Q1
CRM: 01058000023571

[Greg Diamond @grgdmnd]

@AdobeCare It seems like the LRC Prerelease invite for Ticket LRD-422-3405 is stuck. Update 15.1.1 failed to fix the server-side throttle (Case ADB-42703790-V3Q1).
How am I supposed to resolve this sync divergence without the access promised on Jan 23?

[Greg Diamond @grgdmnd]

Hi @AdobeCare @Lightroom, it seems I’m stuck in limbo. Engineering offered a Lightroom Pre-Release forum invite for faster downloads, but no invite/link has been sent and my follow-ups went unanswered. This blocks the next steps they requested. Case ADB-42703790-V3Q1 | Ticket LRD-422-3405 | CRM 01058000023571. Who can trigger the invite today?

[Greg Diamond @grgdmnd]

Hi @AdobeCare @Lightroom, it seems I’m stuck waiting. A week ago you offered to invite me to the Pre-Release forum, but I still haven’t received the invite link or answers to my questions. Case: ADB-42703790-V3Q1. What’s the quickest way to get a clear action plan in writing?

[Greg Diamond @grgdmnd]

Hi @AdobeCare @Lightroom, it seems I’m stuck waiting. A week ago you offered to invite me to the Pre-Release forum, but I still haven’t received the invite link or answers to my questions. Case: ADB-42703790-V3Q1. What’s the quickest way to get a clear action plan in writing?

[Greg Diamond @grgdmnd]

@AdobeCare @Greg @AdobeCare It seems like the conversation has stopped. Silence on Ticket LRD-422-3405 feels like a signal that you’ve given up on Case ADB-42703790-V3Q1.
I’m still here, still blocked, and still waiting for the Sync Engineer.
How do we restart this before Day 60 arrives?

[Greg Diamond @grgdmnd]

@AdobeCare @Greg @AdobeCare It seems like the conversation has stopped. Silence on Ticket LRD-422-3405 feels like a signal that you’ve given up on Case ADB-42703790-V3Q1.
I’m still here, still blocked, and still waiting for the Sync Engineer.
How do we restart this before Day 60 arrives?

[Greg Diamond @grgdmnd]

@AdobeCare It seems like Case ADB-42703790-V3Q1 is falling through the cracks again. Silence doesn’t fix a server-side API failure (Ticket LRD-422-3405). How am I supposed to meet my deadline if we can’t even get a timeline from the Sync Engineer?

[Greg Diamond @grgdmnd]

@AdobeCare It’s been 72 hours since I submitted the config logs for Ticket LRD-422-3405 (Case ADB-42703790-V3Q1).
The data confirms the server is throttling my client (`too many requests`).
How do we ensure the Sync Engineer reviews this today so we don’t lose another week?

[Greg Diamond @grgdmnd]

@AdobeCare Noel, while we wait for the product team to fix the sync, I need practical advice. How can I safely curate my book project files now without creating new sync conflicts?
What is the safest interim workflow to avoid worsening the server divergence while the Engineer works?

[Greg Diamond @grgdmnd]

@AdobeCare It feels like we are falling back into the pattern of “waiting for updates” that go nowhere. Case ADB-42703790-V3Q1 is still critical.
Have you given up on connecting me with the Sync Engineer for Ticket LRD-422-3405 today?

[Greg Diamond @grgdmnd]

@AdobeCare You say Case ADB-42703790-V3Q1 is important “to me,” yet another day passed with zero progress on Ticket LRD-422-3405.
50 days of “updates” without a fix feels like the opposite of important.
How on board is the Sync Engineering team with solving this today?

[Greg Diamond @grgdmnd]

@AdobeCare You say Case ADB-42703790-V3Q1 is important “to me,” yet another day passed with zero progress on Ticket LRD-422-3405.
50 days of “updates” without a fix feels like the opposite of important.
How on board is the Sync Engineering team with solving this today?

[Greg Diamond @grgdmnd]

@AdobeCare @Greg @AdobeCare Thanks for the update, Noel. It feels like we are close to a breakthrough on Ticket LRD-422-3405. How do we make sure this “next step” is the final step (a server-side purge) rather than another round of data collection? I’m ready when you are.

[Greg Diamond @grgdmnd]

@AdobeCare It seems like we are going in circles. I have already “reached out directly” via that link multiple times, which led to Case ADB-42703790-V3Q1 and Ticket LRD-422-3405. How does sending me back to the starting line fix the server-side failure that Engineering has already acknowledged?

[Greg Diamond @grgdmnd]

@AdobeCare It seems like Case ADB-42703790-V3Q1 has been paused for the weekend. Since Ticket LRD-422-3405 confirms the issue, how do we make sure the Sync Engineer sees this first thing this morning? 45+ days blocked on a deadline feels like long enough.

[Greg Diamond @grgdmnd]

@AdobeCare We have the diagnosis (Case ADB-42703790) and the ticket (LRD-422-3405). Now, how does filtering this through support agents who can’t admit it’s a server-side issue help us? How do we stop the game of telephone and let a Sync Engineer fix the divergence?

[Greg Diamond @grgdmnd]

@AdobeCare My logs show 5.7s timeouts & server-side API rejections. Your support says “we’re not sure.” How does denying the math fix the database?
45 days blocked on a book deadline. I have the Engineering Ticket (LRD-422-3405). Why are we hiding the Sync Engineer? #Lightroom

[Greg Diamond @grgdmnd]

@Zexyooo Hi