Item Mapping Migration

We’ve seen the same issue. We raised a ticket a couple weeks ago, but there is no resolution yet. I’ve noticed the same happen with native monday blocks (trigger and action), so it’s not an issue with the custom blocks. I believe it’s an issue with the automation template. However, it should work in the automation builder through the create from scratch functionality.

Ahh thanks! At least it isn’t just me. I’ll create a ticket as well

Hi, ​@workflowpilot did you get any response back? I tried it today and it seems to not work still and giving “No options available” message.

In previous integration recipe builder there was an option to map the input of the item mapping, but here this too is not available (maybe an issue around here, as I followed the response format as per docs too). Still no luck.

​@workflowpilot ​@mitchell.hudson ​@ShubhCoder share your support ticket IDs here so that this can be linked back to them.

Cc: ​@OmerK 

Sure, I raised ticket on 14 May. ID is 4902410.

Haven't received any response yet, apart from automated acknowledgement.

Ticket #4867458 for me

They confirmed with me that the issue was specific to the Automation template. If you build the recipe from scratch it should work as expected

Hi, ​@mitchell.hudson 

Did they give any ETA of when the issue would be fixed, for Automation template? And, for some reason if I try to use the action block directly in recipe (in build from scratch), I am still getting "No options available".

Mine is #4813626, they marked it as Solved, but it’s not Solved.

​@workflowpilot If it’s closed, open another and refer to the closed ticket.

I reopened the same ticket by replying back to it

Just an update on this, I tried again today and it does work if used independently in build from scratch recipe. Initially it does show “No options available” if clicked for the first time, but after few seconds it loads up the item mapping window (which is weird, as atleast it could show some loading animation to avoid confusions).

But main concern in my use case is that, not all action blocks can be used alone and needs to be tied to triggers for it to work properly.

And, it’s been 6days now and I am yet to receive any human response for my ticket raised.

Hi, ​@noa.rapoport 

Could you please look into this issue? As, this is a massive blocker during migration process specially for cases where both trigger & action blocks needs to be coupled for it to work properly.

So far from Slack, I found there are two more developers (who showed up) facing the issue. There tickets are:- #4633437 & #4756153. This issue have been open for a while now, as one (#4633437) raised this on Feb and is yet to receive any solutions.

Looking forward to a resolution on this.

Thank you.

​@ShubhCoder Your ticket has been open since February? 3 months?

No, I raised mine this month. The one I am referring to was raised by another developer on February (and yes it’s been 3months). And, this was the last update received from the support team on the ticket.

Hi there,

I want to touch base as we head toward the end of May. I know how incredibly maddening it is to watch your block function perfectly inside the builder while the template environment refuses to cooperate. It’s a deceptive type of issue that makes it incredibly hard to plan your deployment, and I want to thank you for keeping your cool while we hunt this down.

Our engineering team has progressed from isolating the rendering sequence to analyzing the state serialization layer. Because the block works flawlessly in isolation, they are currently tracing exactly how the configuration data is packaged when a board is cloned from a template. They are investigating whether a security scope or a unique identifier is being stripped or altered during the background duplication process, causing the template environment to misinterpret a completely valid block configuration.

While I don't have a definitive fix or a concrete release ETA to hand over to you today, please rest assured that this investigation is highly active. I am inside the developer notes every day to review their testing outputs, keep the momentum going, and ensure this doesn't get pushed aside by other core platform updates.

Thank you again for your patience and for partnering with me through this deep dive.

Here is the latest update I got overnight:
 

Our engineering team has isolated the breakdown to the platform's automation hydration layer. Specifically, they are analyzing why the template engine fails to properly carry over and map the block dependencies and unique identifiers during a template duplication sequence, causing the configuration to drop.
 
While I don't have a definitive deployment timestamp or a concrete ETA to hand over to you today, please rest assured that your account context is tied directly to this open bug tracker item. I am monitoring their internal review notes every single day to ensure this keeps moving forward through the pipeline. 
 

Hi ​@mitchell.hudson did you get any further update on this?

As for me, I am not receiving any useful information just that no ETA is there and team is looking into it (from last 1.5weeks).

No nothing else yet…

Hi all,

Just sharing an update I received from support (after daily pings)

I want to be transparent that I cannot provide an exact ETA for the fix yet. I don’t want to promise a specific date before the development team confirms the final scope and release path. What I can share is that we are expecting to have either a significant update or a final outcome within this month, and I’ll keep you updated as soon as I receive anything meaningful from the team.

I think we should have some news regarding what the team is going to do for the issue, hopefully by this month end🤞. But again no ETA of when this will be solved.

Do share, if any of you get updates from support that might give some hope 😥.

Hi all,

Just sharing an update I received from support team. Unfortunately, they cannot commit to ETA this week too (as it’s happening currently)

At the moment, the issue is still under review with our development team. They are continuing to investigate the behavior around the dynamic Object field showing “No options available” even though the schema endpoint appears to return valid dynamic values.
 
I want to be transparent that I still do not have a confirmed fix ETA or final resolution path to share yet. However, I am continuing to follow this closely internally, and I’m expecting to have a more meaningful status update around the end of this week or the beginning of next week.
 
I’ll keep checking with the team and will share any progress, findings, workaround, or next step with you as soon as I receive it.

If any of you have any kind of updates, please do share with us. 🙏